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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful context beyond those flags: observations are 'append-only', they are unverified owner reports, and agents cannot record observations. This clarifies both the data model and the trust boundary, which is exactly the kind of behavioral caveat an agent needs.

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 no filler. The first sentence states the action and object, the second adds necessary epistemic caveats, and the third states an important agent restriction. Every sentence earns its place and the structure is easy to scan.

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?

For a read-only listing tool with full schema coverage, an output schema, and safety annotations, the description is complete. It explains the purpose, the provenance and reliability of the data, and the agent's inability to write. Nothing essential for correct invocation is missing.

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 description coverage is 100%, and each parameter already has a meaningful description: limit has bounds and ordering, before explains pagination tokens, and job_id names its source. The description itself adds no parameter-specific detail, so it correctly stays at the baseline of 3.

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 uses a specific verb ('Read') and identifies a precise resource: the owner's append-only observations about an unknown write. It also distinguishes itself from status/verification/retry tools by explicitly stating it is 'not verified provider facts, a changed job status, or permission to retry', making its purpose unambiguous.

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 clear context for when to use the tool: to inspect owner-side reconciliation evidence for an unknown write. It explicitly states what the observations are not, which helps an agent avoid misusing the tool as a source of verified facts or retry authorization. It does not name a specific sibling alternative, so it falls short of a 5.

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