delimit_agent_handoff

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Hand off an agent task', implying mutation, but lacks details on side effects, whether the current task is paused, or any confirmation. The description is insufficiently transparent.

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 extremely concise (one sentence, 10 words) with no fluff. However, it may be too brief given the tool's complexity, but conciseness is about efficiency, which is achieved.

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?

Although an output schema exists (which could describe return values), the description lacks context about the handoff process, prerequisites, and behavior. For a tool with no annotations and minimal description, this is incomplete.

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?

The input schema has 3 parameters (task_id, to_model, context) with 0% description coverage. The description does not mention any parameters or explain their meaning, leaving the agent to infer from names alone.

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 clearly states the verb 'Hand off' and the resource 'agent task', specifying it is to a different AI model (Pro). This distinguishes it from other handoff tools like delimit_handoff_create, but it does not elaborate on what 'hand off' entails.

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 among the many siblings (e.g., delimit_handoff_create, delimit_handoff_acknowledge). It does not mention when not to use it or any prerequisites.

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