Record a dispatch handoff

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

Discloses it's informational only, appends to audit log, and that the latest dispatch overwrites previous. Beyond annotations which only indicate non-readOnly and non-destructive.

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?

Single paragraph with key info front-loaded. Could be slightly more structured but no wasted 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?

For a logging tool with no output schema, description provides sufficient context: when to use, parameters, behavior. Lacks response format but probable simple acknowledgment.

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?

Adds context for model (use when worker is sub-agent) and parallel (running alongside other dispatches). The schema covers 67% of parameters, and description fills in gaps for usage.

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 it records who is actively working a ticket as an audit event. It distinguishes from siblings like set_status and get_agent_monitor by focusing on the dispatch handoff.

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?

Explicitly tells when to call: right after set_status 'In Progress' for sub-agent handoffs and when taking back with orchestrator. Also states it never moves status and that the newest call wins.

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