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

Annotations already establish readOnly/idempotent/non-destructive/openWorld, so the bar is lower; the description still adds real value by warning that public statuses do not prove ISP acceptance or installation confirmation, i.e. interpreting what the returned evidence can and cannot be trusted for. It does not add auth, rate-limit, or pagination context, but the safety profile and output schema make that less critical.

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?

Two sentences, zero filler, with the purpose and the trigger condition front-loaded and the caveat second. Every clause earns its place.

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?

With annotations covering safety and an output schema covering return shape, the description only needs to supply purpose, usage, and interpretation — and it does all three. The remaining gap is not distinguishing itself from the other read-oriented siblings (validate_order, check_availability).

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 0%, so the description should carry parameter meaning; it names checkout_id and implicitly locates its provenance in a prior create_order call, which is useful. However it adds no format, constraint, or sourcing detail beyond the self-explanatory name.

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?

States a concrete verb (Retrieve) and resource (recorded fulfillment evidence for an order), and ties it to a sibling by referencing create_order as the trigger. It does not explicitly distinguish itself from validate_order or check_availability, so it stops short of a 5.

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?

Gives a clear usage trigger — use it 'especially after a lost or uncertain create_order response' — which is exactly the ambiguous case an agent needs steering on. It offers no explicit when-not-to-use or named alternative for the validate/check paths, so no 5.

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