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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only that it returns handoff state plus a ticket, which overlaps with the existing output schema, and discloses nothing about permissions, scoping, or side effects.

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?

It is a single short sentence with no padding, which is appropriately sized, but the leading phrase is front-loaded with an ambiguous action verb rather than the resource being read, hurting clarity.

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 one-parameter read tool with an output schema, the description still needs to define what a 'handoff' is and when the tool should be selected over its many siblings. The jargon-heavy fragment leaves an agent unable to confidently invoke it.

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?

There is one required parameter (handoff_id) with 0% schema description coverage, and the description never explains it. The description must compensate for the coverage gap and it does not, so an agent has no idea what form a valid handoff_id takes.

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 fragment 'Hand to a person' reads like a transfer/escalation action, but the rest of the sentence ('the state of a handoff and its Navigator desk ticket') describes a read. The intent is ambiguous and the resources named ('Navigator desk ticket', 'media program') are internal jargon that don't distinguish it from siblings like resolve_actor or get_banner_card.

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 trailing clause 'where the media program has no agent' hints at a triggering condition, but it is cryptic and gives no explicit when-to-use, when-not-to-use, or named alternative. No sibling is referenced for routing.

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