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

The description goes beyond annotations by explaining the internal packaging: HANDOFF.md at the root of a zip, inclusion of files, and a single handoff URL. It also describes what the receiving model experiences (briefing, file manifest, download commands). Annotations already indicate external side effects, so the added specificity is useful.

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 one solid paragraph that is fairly detailed but front-loaded with the main purpose. Every sentence contributes to explaining the mechanism and how to use the URL, though it could be trimmed slightly without loss.

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?

With no output schema, the description fully explains the result: a handoff URL that the next agent fetches to receive briefing and download commands. It also covers the key parameters (files, transcript) in context, creating a complete mental model for the tool.

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 provides 100% coverage with detailed descriptions for all parameters. The tool description mostly restates that the transcript becomes HANDOFF.md and files are included, which the schema already says. It doesn't add substantial new parameter-level meaning.

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 tool's specific purpose: to hand a full working context to another model, packaging a transcript and files into a zip and returning a handoff URL. It explicitly mentions the key elements (instructions, conversation summary, task state) and distinguishes itself from sibling tools that share files or text.

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 gives clear context for when to use the tool ('to hand your full working context to another AI') and details the handoff flow, but it doesn't explicitly mention alternatives or when NOT to use it. Since siblings are share_file/share_text, the usage context is reasonably clear.

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