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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations by clarifying that it does not modify, allocate, receive, or ship stock, and by disclosing the 'up to 100 receipt lines' return scope.

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 two tightly written sentences with no wasted language. The core operation and record-ID lookup are front-loaded, followed by the important non-mutation boundary.

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 tool with rich annotations but no output schema, the description gives enough context to understand the operation and return scope. It could be slightly more complete by clarifying that exactly one ASN is returned for the given ID and what happens when no record matches.

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 the schema already explains that record_id is an Infoplus numeric record ID from a search result, as a string. The description repeats the numeric-ID concept but adds no syntax or format details beyond the schema.

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 an Infoplus advance shipping notice and up to 100 receipt lines by numeric record ID. It is clear what the tool does, though it does not explicitly name or route to the sibling search tool, and the plural 'notices' is slightly ambiguous for a lookup by one ID.

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 implies usage by saying the lookup is by Infoplus numeric record ID, and the schema notes the ID comes from a search result. However, it does not explicitly say when to use this tool versus infoplus_search_asns or state prerequisites for obtaining the ID.

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