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

With no annotations, the description carries the burden well by disclosing that the operation is read-only in effect, public, non-authorizing for payment, and bounded in data exposure. It still omits authentication requirements and error behavior, so it is not exhaustive.

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?

Two sentences, front-loaded with the core action and return fields, followed by precise exclusions. No sentence is wasted.

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?

The description lists the fields returned, which helps because no output schema exists, and it clarifies important boundaries. It still leaves gaps around the ticketId input and access/error behavior, making it adequate but not fully complete.

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 sole required parameter, ticketId, is never mentioned in the description. Schema description coverage is 0%, so the description does not compensate by explaining what the identifier refers to beyond the schema's UUID format and pattern.

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 states a specific verb and resource: reading public recovery status for a buyer's work ticket. It also distinguishes this from related operations by naming what is included (state, quote terms, payment reference, result hash) and what is not exposed (task input, result bytes).

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 is implied by 'Read public recovery status', and the description gives two exclusions: it does not expose result bytes and does not authorize payment. However, it never explicitly says when to choose this tool over siblings like read_work_ticket_result or pay_work_ticket_quote.

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