Get Parcel Delivery

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds context that events are 'cached' and limited to 'active or recent' API response, which informs the user about data freshness and scope. No contradiction.

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, front-loaded sentence that is wholly informative; no filler or redundancy.

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 three-parameter tool with no output schema, the description covers the action, target, and return value. It does not explain the impact of filter_mode and response_format, but the schema supplies those defaults. The description gives enough context for a straightforward use case.

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%. The description clarifies the purpose of 'tracking_number' by emphasizing exact match, and hints at 'filter_mode' via 'active or recent'. However, it provides no guidance on 'response_format' default or alternatives, leaving the schema enums to carry that meaning.

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 uses the specific verb 'Find' and identifies the resource as 'one delivery' via 'exact tracking number', with the outcome 'return all of its cached events'. This clearly differentiates from sibling 'parcel_list_deliveries' which lists multiple deliveries.

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 implicitly conveys that this tool is for locating a specific delivery when the exact tracking number is known, distinguishing it from listing tools. However, it does not explicitly state when not to use it or mention alternative tools by name, so it falls short of a 5.

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