get_delivery

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

Annotations (readOnlyHint, idempotentHint, destructiveHint=false) already declare the safety profile, but the description adds no behavioral context beyond the basic fetch action. It does not mention return format, error behavior, or any side effects, so it adds no value beyond what annotations already provide.

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 a single, front-loaded sentence with no wasted words. It is concise and to the point, though it is terse enough that it could be mistaken for a tautology if not for the specific noun 'delivery'.

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 simple 1-parameter getter, the description is minimally viable. However, without an output schema, the agent might expect more detail about what the response contains or potential errors. The presence of annotations and the self-explanatory param mitigate the absence, but the description leaves gaps in return value and edge-case handling.

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?

The input schema covers 100% of the parameter semantics, with a clear description for 'delivery_id' ('the id of the delivery'). The description adds nothing about the parameter, so the baseline of 3 is appropriate since the schema does the heavy lifting.

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 'Fetch a delivery' states a clear verb and resource, indicating a retrieval operation for a single delivery. However, it does not explicitly differentiate itself from the sibling tool 'list_deliveries', which would provide the contrast between fetching one versus multiple records.

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?

No guidance is provided on when to use this tool versus alternatives such as 'list_deliveries' or 'issue_delivery'. The description lacks any contextual cues about scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the name and parameters alone.

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