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

With no annotations, the description carries the full burden, and it delivers: payment amount and address, HTTP 402 on unpaid requests, JSON response after a valid X-PAYMENT, chunk retrieval semantics, and the explicit note that this endpoint is not a new SKU. This is exceptional disclosure for a paid endpoint.

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?

The description is dense but contains no filler; every sentence conveys operational information. It could be slightly better structured for readability, but the front-loaded endpoint and payment details make it efficiently scannable.

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?

Even without an output schema or annotations, the description tells an agent everything needed to invoke it correctly: how to select chunks, how to pay, what HTTP error to expect, and what happens after payment. The only missing piece is detailed JSON shape, which is not required here.

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 descriptions cover all four parameters (id, page, before, x_payment) with usage details, so the description does not need to restate them. It adds pricing and HTTP behavior but not new parameter-level meaning, so the baseline 3 applies.

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 clearly specifies the resource (UK AAIB investigation-report text) and the operations available: a plain GET returns the newest chunk, ?id returns one official text, and ?before returns an older chunk. It also identifies the exact endpoint, making it easy to tell apart from report-tool 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?

It provides concrete usage conditions: plain GET for newest chunk, ?id for the official catalog text, ?before with an id or date for older chunks, and omitting before for newest. It does not explicitly name alternative tools or exclusion cases, but the operation-specific guidance is clear enough.

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