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

Annotations already declare destructiveHint=true, non-idempotent, openWorld, so the description's only added context is that the result is a PDF link. It never explains what the 'destructive' aspect means here — e.g., whether generating a SCAN form finalizes or consumes a batch/ship date, or whether it can be regenerated. For a destructive, non-idempotent tool that is the single most important thing 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?

A single compact sentence with the resource and output front-loaded and no filler. It is arguably slightly under-specified rather than too long, which is a completeness issue rather than a conciseness one.

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?

All parameters are optional and fully documented in the schema, and the description covers the return type (PDF link), so nothing critical is missing. However, for a destructive, non-idempotent generation tool with no output schema, the description should say what generating a form does to the underlying batch/labels and whether it is repeatable.

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%, so all three parameters including the precedence rule (batch_id ignores ship_date) are already documented. The description restates the ship_date scoping but adds no format, default, or interaction detail beyond the schema, so baseline 3 applies.

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?

Identifies a specific, recognizable resource (USPS End of Day SCAN Form) and states the output form (a PDF link), which lets an agent tell it apart from the read-only sibling list_scan_forms. The generative verb is only implied by the title rather than stated in the description itself, so it is clear but not perfect.

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 explicit when-to-use statement, no prerequisites, and no mention of the obvious alternative list_scan_forms. The only guidance is embedded in the schema ('only the labels of this batch', 'default: today'), which the description does not reinforce or contextualize.

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