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

Beyond the annotations, the description discloses billing impact ('No charge'), authentication requirements ('OAuth or a key for the owning workspace'), data freshness limits ('Does not itself refresh mailing status'), and error handling guidance ('Inspect the body for not_found'). These are substantive behavioral traits an agent needs before invoking the tool.

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 front-loaded and compact, with each short sentence adding practical information: billing, read behavior, freshness limitation, and error inspection. There is 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?

Given a simple one-parameter read tool, rich annotations, and an output schema, the description covers authentication, billing, staleness, and not-found handling well. The main missing piece is clarity about the 'id' parameter itself, which prevents a full 5.

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 schema has 0% description coverage for the single required 'id' parameter, so the description must carry the burden. It only says lookup is 'by id' and does not clarify whether this is a job id, letter id, tracking id, or its expected format, leaving meaningful ambiguity.

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: read stored job status and tracking by id. It is clearly more than a tautology, but it does not explicitly differentiate this lookup-by-id tool from siblings such as list_jobs or download_job_document.

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 gives clear usage context by specifying lookup by id and warning that the tool does not itself refresh mailing status. It does not name alternatives or state a full when-not-to-use rule, 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.