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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, whether it requires authentication, what happens if the order is not found, or any rate limits. The description is essentially a restatement of the tool name with no behavioral context.

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, concise sentence with no wasted words. However, it is almost too terse given the lack of other information, but from a pure conciseness standpoint it is efficient.

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?

Given no annotations, no output schema, and 0% parameter description coverage, the description is completely inadequate for a tool that likely returns detailed tracking information. It does not explain what the traces contain, the return format, or how to handle errors. An agent would struggle to use this tool correctly without additional context.

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 0% and there is one required parameter (order_no) with no description in either the schema or the tool description. The description implies that an order number is needed but does not specify its format or source. The baseline for 0 parameters is 4, but here we have a parameter that is completely undocumented, so the score is lower.

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 states a resource (express tracking traces for a shipped order), which gives a sense of what the tool does. However, the phrasing is slightly awkward and it does not clearly differentiate from the sibling get_order_status, which could also return order-related information. The purpose is vague about whether it returns tracking events, carrier info, or logistics status.

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 tool versus alternatives such as get_order_status. No context about prerequisites or exclusions is provided, leaving the agent to infer usage from the name alone.

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