Track DHL Shipment

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

Annotations already declare readOnlyHint and idempotentHint, so the bar is lower. The description adds valuable behavioral details: returns current status, delivery events timeline, origin/destination, estimated delivery date, service type, and official data for 220+ countries. No contradictions with annotations.

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 efficient sentences: first sentence states outputs, second sentence states service coverage and geographical scope. No wasted words, well front-loaded with the main purpose.

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 tracking tool with one parameter and an output schema, the description covers all essential information: what it does, what data it returns, and its scope. No gaps given the annotations and output schema.

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 100% with a detailed description including examples. The tool's description reinforces that the parameter is a tracking number and lists the supported services. This adds context 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 clearly states the action (track a DHL shipment), the resource (tracking number), and the outputs (status, events, origin/destination, etc.). It distinguishes from sibling tools like logistics.tracking.list or logistics.tracking.register by specifying DHL and the full set of returned data.

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 explicitly mentions when to use the tool (to track a DHL shipment) but does not include when not to use it or mention alternative tools. However, the purpose is clear enough that an agent can infer its context relative to siblings.

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