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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds real context beyond them: the token is 'separate' and 'long-lived', and the call does not authorize confirmation or resume browser work. The note that synthetic receipts never become real status is useful semantic disclosure. It stops short of covering error behavior or what happens with an expired token.

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?

Three short sentences with the core capability front-loaded, followed by boundary conditions. Dense and near waste-free, though the negations could be consolidated to read more smoothly.

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?

No output schema exists, so the description should convey what comes back; it says 'booking/payment confirmation' but gives no indication of shape, fields, or what a non-confirmed result looks like. Given two required params at 0% schema coverage and no annotations covering failure modes, this is adequate but leaves gaps.

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 0%, so the description carries the burden. It clarifies that confirmation_token is separate from the journey reference and is long-lived, which is genuinely useful, but journey_id is never explained and no format or sourcing guidance is given for either parameter.

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 and resource: 'Read only booking/payment confirmation for a Spann reference.' The scope is narrow and identifiable, though 'Spann reference' is domain jargon an agent may not resolve from the definition alone, and no sibling is named explicitly.

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 exclusions ('does not resume browser work or authorize confirmation') imply when this tool is the wrong choice, but they are stated as negations rather than routing to a concrete alternative such as prepare_reservation_action or get_spann_journey_status. Usage is inferable but not spelled out.

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