orders_track_order

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 explicitly state that this is a read-only operation, nor does it mention any prerequisites, potential latency, or data freshness. The term 'current' hints at timeliness but lacks detail about what is returned or how events are ordered.

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 sentence that is front-loaded with the primary action and outcome. Every word contributes meaning with no redundancy or filler.

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-parameter read tool, the description provides the core purpose but lacks details about the return format, such as whether carrier events are a list, how many events are included, or what fields are present. Since there is no output schema, these gaps matter. Still, the tool's simplicity makes this minimally adequate.

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 the parameter description 'Order to track.' The tool description adds context about shipment tracking, but does not significantly enhance the understanding of order_id beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 a specific action: 'Get the current shipment tracking status and carrier events for an order.' This distinguishes it from sibling tools like orders_get_order (which likely retrieves order details) by focusing on shipment tracking and carrier events.

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 implies usage for tracking shipments by the phrase 'shipment tracking status', but it does not explicitly mention when to use this tool versus alternatives like orders_get_order or orders_list_orders. No exclusions or alternative tool references are provided.

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