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

Annotations already cover readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses that failure rows without receipts are included, that args_json is permission-gated with an args_withheld marker, and that secrets are redacted. This is exactly the contextual value the description should add, though it omits pagination/response-size behavior.

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?

Front-loaded with the action and resource, then the return surface, then the permission/redaction caveat — a sensible priority order. It is dense but every clause carries information; no filler.

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 sensibly enumerates the returned surface (args_hash, hash chain, response_summary, timestamps, receipt_id) and explains conditional omission of args_json, which is enough to set expectations. Missing only edge cases like not-found behavior or response size.

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?

With one parameter and 0% schema description coverage, the description only restates that the id identifies an execution row; it gives no format, provenance (where to obtain the id), or error behavior for unknown ids. Since parameter count is one, the burden is light, but the description still adds only marginal meaning beyond the schema.

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 a single execution row by id') and clarifies the scope by noting it includes failure-status rows that never got a receipt — implicitly distinguishing it from the receipt-oriented siblings. It never names get_receipt or list_recent_receipts directly, so an agent must infer the routing rather than being told.

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 'by id' framing implies the lookup use case, but there is no explicit when-to-use/when-not statement and no named alternative. Given the siblings fleet__get_receipt and fleet__list_recent_receipts, a clear rule (e.g. 'use get_receipt when you have a receipt id') would materially help.

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