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

Annotations already cover read-only, idempotent, non-destructive, so the description correctly spends its words elsewhere: it discloses that pending is a success state and not an error (a genuine pitfall), that payload format depends on handoff type, and that the call does not mutate the handoff. Missing only failure behavior for an unknown or malformed id.

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?

Four short front-loaded sentences, each carrying distinct information: the primary action, the format variants, the pending edge case, and the non-mutating guarantee. Nothing is repeated from the annotations or schema.

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 takes on the burden of describing returns and does so adequately — named payload shapes plus the pending state. Safety is covered by annotations and the unaffected-by-call note closes the mutation question.

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 coverage is 100% and the single id parameter is fully documented as 'Handoff id, hnd_...'. The description adds only that the id scopes to one handoff on this account, so baseline 3 is appropriate.

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?

States a specific verb (read) and resource (the completed answer for one handoff), and further specifies the return shape per handoff type: PDF paths plus recognized handwriting, or JSON answers for HTML/HUI. An agent can tell this apart from get_handoff_status without opening a schema.

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?

Usage context is implied rather than stated: you call this when you want the submitted answer, and the pending note tells you what happens before submission. It never names get_handoff_status or wait_for_handoff as the alternative, so the agent must infer the routing from sibling names alone.

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