delimit_agent_handoff

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

With no annotations, the description carries full burden. It discloses side effects: writes a handoff record and updates assignee. This is valuable behavioral context. Could add details on permissions or idempotency, but the current disclosure is strong.

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?

Description is concise and well-structured: first sentence defines core action, then usage conditions, then sibling contrast, then side effects. Every sentence is purposeful and front-loaded. No unnecessary words.

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's simplicity (handoff, 3 parameters) and presence of an output schema, the description covers all critical aspects: purpose, when to use, sibling differentiation, and side effects. An agent can make an informed decision.

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 coverage is 100%, so the baseline is 3. The description does not add parameter details beyond the schema (task_id, to_model, context). It repeats the schema's context description but no extra semantics. Adequate but not enhanced.

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?

Description clearly states the tool's purpose: 'Hand off an agent task to a different AI model (Pro).' It differentiates from siblings by explicitly contrasting with delimit_agent_complete and delimit_agent_dispatch, making the unique function unmistakable.

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?

Provides explicit when-to-use scenarios (executor blocked, cross-model review) and when-not-to-use (close out, create new). Directly names sibling alternatives, offering clear guidance for selection.

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