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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine value by disclosing the shape of the result: forms grouped per ship-from address, each with a PDF link, plus identification of labels that lack a SCAN form. It does not address pagination, volume, or freshness of the data.

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?

A single compact sentence with no filler, and the core noun (USPS SCAN Forms) is front-loaded. The trailing clause 'with their PDF links and labels still without one' is compressed to the point of ambiguity, slightly undercutting an otherwise efficient structure.

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 zero-parameter read tool with annotations covering safety and no output schema, the description covers what is returned at a high level. It omits grouping/ordering behavior and whether the PDF links are pre-signed or time-limited, which are the remaining things an agent would want to know before calling.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. Schema coverage is 100% and the schema is empty.

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 names the resource (USPS SCAN Forms) and the organizing key (Ship From Address), plus the payload (PDF links, labels lacking a form). However, it never states the operation as a verb ('list/retrieve') and the phrasing 'labels still without one' is telegraphic, so an agent must infer that this is a read-only enumeration rather than a diagnostic about missing forms.

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?

There is no statement of when to call this versus create_scan_form or list_ship_from_addresses, and no prerequisite or exclusion guidance. The only implicit signal is the 'list' prefix in the name, which the description does not reinforce.

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