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

The description says 'Hand to a person,' which implies a state-changing action, while annotations declare readOnlyHint=true. This is a direct contradiction. No other behavioral context (auth, rate limits) is provided.

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 sentence, but it is convoluted, ambiguous, and not front-loaded with a clear purpose. The structure hinders rather than aids comprehension.

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?

An output schema exists so return values needn't be explained, but the description fails to identify the tool's operation or the parameter, leaving 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?

Schema description coverage is 0% and the sole parameter handoff_id has no description in either the schema or the tool description. The description does not mention the parameter at all, leaving its meaning entirely undocumented.

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 does not clearly state a verb+resource. 'Hand to a person' suggests an action (handoff) while the rest describes retrieving state, making the tool's purpose ambiguous and difficult to distinguish from siblings.

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?

Only a fragment of a condition ('where the media program has no agent') implies when it applies, but there is no explicit when/when-not guidance or mention of alternatives.

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