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

With no annotations, the description carries the full behavioral burden, and it does disclose a non-obvious trait: the carrier status is refreshed only when older than 12 hours, implying cached/stale reads and possible upstream carrier calls. It omits permissions, failure behavior, and cost/latency implications of that refresh.

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, front-loaded with the scope before the refresh nuance. The endpoint-mapping clause is marginally useful for developers but is the weakest-earning sentence for an agent.

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 single-resource read with a 2-param, fully documented schema and no output schema, the description covers scope, staleness semantics, and the underlying endpoint. Missing only explicit sibling routing and error/empty-state behavior.

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 already documented. The REST mapping ('GET /api/Labels/Status/{labelId}') confirms labelId is the path key, but adds no format, range, or intentId usage guidance 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?

States a specific verb+resource ('current shipment status') and scopes it to 'one label', which implicitly separates it from the plural sibling GetShipmentStatuses. It does not name that sibling explicitly, so differentiation relies on the reader inferring it from the singular/plural distinction.

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 explicit guidance on when to use this versus GetShipmentStatuses, GetLabelTrackingStatus, or GetLabel, all of which are adjacent in the sibling list. The 'when older than 12 hours' clause describes internal refresh behavior, not a usage condition for the caller.

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