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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's contribution is limited to noting that results include recent tracking events. It does not disclose data freshness, whether the carrier is queried live, rate limits, or behavior when the carrier has no events yet.

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?

One sentence, front-loaded with the resource and result content, with no filler. It is efficient, though the brevity comes partly from omitting guidance rather than from tight editing.

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 no output schema, the description carries the burden of describing return values; it sketches them (status plus recent events) but not the shape, count, or freshness of those events. For a read-only tracking tool with full schema coverage, this is adequate but leaves real gaps.

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%, so both parameters are documented, establishing a baseline of 3. The phrase 'label usage id' does add a small disambiguation over the schema's 'Label usage id (integer)', but it adds nothing about intentId's correlation-ID semantics or format.

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 specific resource (carrier tracking status plus recent tracking events) scoped to a label usage id, which is clear and concrete. It lacks a verb and never distinguishes itself from close siblings like GetShipmentStatus, GetShipmentStatuses, or LookupByTrackTrace, so an agent must infer the boundary.

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 when-to-use guidance, no prerequisites, and no named alternatives despite a crowded sibling set of tracking/lookup tools (GetShipmentStatus, GetShipmentStatuses, LookupByTrackTrace, InvestigateLabelByTrackTrace, get_label_log). The agent is left to guess which tracking tool applies.

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