delimit_agent_handoff

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are absent, so the description must fully disclose behavior. It only states a handoff action but does not explain side effects, whether the task is paused/resumed, authentication needs, rate limits, or if the original model is retained. Essential behavioral details are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it is too brief given the tool's complexity and lack of schema descriptions. It does not earn its place as it omits critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 parameters, no schema descriptions, no annotations, and the output schema existence but unknown content, the description is grossly insufficient. It does not explain the handoff process, what happens to the task, or the return value. The tool cannot be properly used based on this description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with no parameter descriptions. The description adds no meaning for task_id, to_model, or context beyond the action. It does not clarify constraints, formats, or expected values (e.g., model names). The description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Hand off an agent task to a different AI model (Pro).' It clearly specifies the verb (hand off), resource (agent task), and target (different AI model, specifically Pro). This helps distinguish from sibling tools like delimit_handoff_create or delimit_session_handoff, though not explicitly compared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like delimit_handoff_create or delimit_session_handoff. There are no conditions, prerequisites, or context for appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.