You are building developer productivity tools using the Claude Agent SDK. The agent helps engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate code, and automate repetitive tasks. It uses the built-in tools (Read, Write, Bash, Grep, Glob) and integrates with Model Context Protocol (MCP) servers.
After adding an MCP server with specialized code refactoring tools (extract_function, rename_variable, inline_function), You notice the agent still uses basic text manipulation via Write and Bash sed commands for refactoring tasks. The MCP server is connected and healthy.
Examining the configuration, you find each MCP tool has a minimal description like
"extract_function: Extracts a function from code."
What's the most effective way to improve adoption of the MCP refactoring tools?

• A. Accept this as expected behavior since simpler tools like sed are more predictable than specialized refactoring tools.
• B. Enhance the MCP tool descriptions to explain when each tool is preferable to text manipulation and clarify expected inputs and outputs.
• C. Implement a request classifier that detects refactoring intent and automatically routes those requests to the MCP server before the agent processes them.
• D. Remove the Write tool from the agent's configuration for refactoring sessions so it must use the MCP tools for code modifications.

Your update_user_profile tool accepts a user_id (required) and an optional fields_to_update object. In testing, Claude frequently omits user_id or passes incorrectly structured data. What is most critical for helping Claude understand what parameter values to provide?

• A. Strict JSON Schema type constraints marking user_id as required and defining fields_to_update as an object type
• B. Detailed error responses explaining why invalid parameter values were rejected
• C. Verbose parameter names encoding format hints, such as user_id_string_uuid_format
• D. Clear parameter descriptions explaining expected format, such as "user_id: UUID of the user to update (required)"

Your control_device tool manages smart home devices through external APIs. When a device doesn't respond within the timeout period, the tool returns an error. Production logs show that the agent simply tells users "the device is not responding" without offering helpful next steps. Which error response structure would best enable the agent to provide useful follow-up?

• A. Set is_error: true with a brief "Device offline" message and provide a separate tool the agent can call to retrieve context-specific troubleshooting suggestions.
• B. Set is_error: true with a message explaining the likely cause and suggesting troubleshooting steps the agent can offer the user.
• C. Set is_error: false with an optimistic message indicating the command was dispatched successfully but device acknowledgment is still pending.
• D. Set is_error: true with a structured technical error containing the device ID, timeout duration, and raw API response code for debugging purposes.

The coordinator agent has AgentDefinitions configured for all four specialized subagents, each with appropriate descriptions, prompts, and tool restrictions. During testing, you notice the coordinator correctly reasons about when to delegate - it generates messages like "I'll ask the web search agent to find sources on this topic" - but no subagent execution ever occurs. The coordinator then proceeds as if the delegation happened and continues with incomplete information. Logs show no errors. What is the most likely cause?

• A. The AgentDefinitions are configured correctly, but the coordinator's system prompt doesn't explicitly list the available subagent types, preventing the model from knowing they can be invoked.
• B. The coordinator's allowedTools configuration doesn't include "Task", so while it can reason about delegation, it cannot invoke the tool required to spawn subagents.
• C. The coordinator's max_tokens setting is too low, causing the Task tool invocation to be truncated before the subagent type parameter can be specified.
• D. Subagent context isolation means task descriptions from the coordinator don't automatically reach subagents; you need to configure explicit context forwarding in ClaudeAgentOptions.

An enterprise wants Claude responses to remain professional across every interaction. Where should tone instructions primarily reside?

• A. User prompt only
• B. API key description
• C. Retrieved documents
• D. System prompt