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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing beyond the return fields. It does not state that this is a read-only lookup, what happens when the labelId is unknown, or any permission/rate constraint. 'Full details' is the only behavioral hint, and it is weak.

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 sentence with zero filler, front-loading the identity of the resource and then the value it returns. Nothing could be trimmed without losing information.

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 field enumeration usefully tells the agent what comes back, and the two-parameter surface is simple. However, in a toolset containing FindLabel, GetLabelsForOrder, ListRecentLabels, and get_label_log, the description never positions this tool, which is the main completeness gap.

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 100%, so both parameters are already documented in the schema (labelId as 'Label usage id (integer)', intentId tied to RecordUserQuestion). The description restates the label-id concept but adds no format, sourcing, or usage nuance for intentId, so the baseline 3 applies.

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 and resource ('Full details for one label usage id') and enumerates the payload (order link, carrier, contract, product), which is more than a restatement of the name. It does not distinguish itself from close siblings like FindLabel, GetLabelsForOrder, or SearchShippingLabels, so an agent must guess which retrieval tool applies.

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?

There is no guidance on when to use this versus the many sibling lookup tools (FindLabel, GetLabelsForOrder, ListRecentLabels, InvestigateLabelByTrackTrace). The phrase 'one label usage id' hints at single-item lookup, but the agent is left to infer the selection rule entirely.

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