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

With no annotations, the description carries the full burden. It usefully discloses that the evidence is redacted, lists the kinds of evidence returned, and specifies the required auth scope, but it does not describe error behavior, pagination, or limitations on what the evidence covers.

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 tool's purpose and then the prerequisite. Every clause adds useful information with 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?

There is no output schema or annotation coverage, but the description sufficiently explains what evidence is returned and what is required to call it. Remaining gaps are minor for a single-parameter read tool: error behavior, pagination, and sibling routing are not covered.

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 single operationId parameter has 0% schema description coverage, so the description must compensate. Saying it requires an assigned operation adds meaning beyond the schema by implying the ID must refer to an operation assigned to the caller, but it does not explain how to obtain the ID or further constrain the UUID.

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 redacted operation evidence. It also names the contents (result hash, settlement record, delivery receipt summaries), which helps distinguish it from the sibling read_assigned_delivery_receipts, though it does not explicitly contrast the two.

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 description gives prerequisites: an assigned operation and operations:read scope in the Authorization header. It does not explicitly say when to use this versus list_assigned_operations or read_assigned_delivery_receipts, so usage is implied rather than fully guided.

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