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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond them by disclosing the shape of the result: layout, per-field digits and meaning, check-digit verdict, service type code row, each with supporting passage.

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?

One front-loaded sentence with no filler, though it is a long compound clause listing output components. Every element listed is content-bearing, so the density is justified.

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 single-parameter read-only decode tool with an output schema and full annotation coverage, the description gives enough to call it correctly and set result expectations. Only input-format edge cases remain unaddressed.

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 coverage is 0% and the schema only says 'string, maxLength 80'. The description compensates partly by identifying the accepted value as an IMpb package barcode or tracking number, but it never states character rules, acceptable lengths, or what happens with a malformed input.

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+resource: reading a package barcode/tracking number (IMpb) to decode its layout and fields. That is clearly distinct from siblings like diff, define, or search, though no sibling is named explicitly.

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 usage is implied by 'Read a package barcode or tracking number (IMpb)' – an agent can infer it is for exactly one barcode string. However, there is no explicit when-to-use guidance, no exclusions (e.g. non-IMpb barcodes), and no routing to alternatives such as lookup or search.

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