Get order status

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

With no annotations provided, the description carries the full burden. It discloses the data returned, the session-based auth requirement, and the different behavior with and without order_number. It does not mention edge-case behavior like invalid sessions or nonexistent orders, but the core behavioral contract is clear.

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 with no filler. The first sentence states the purpose and expected output; the second explains the key branching parameter behavior. Everything present earns its place.

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?

The tool has no output schema, and the description compensates by summarizing the returned fields. It covers authentication context, single vs. list behavior, and optional parameters. Minor gaps like response format details and error behavior are acceptable for a simple lookup tool.

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 the baseline is 3. The description adds meaningful relational semantics: order_number changes the call from a list to a single-order lookup, and pageSize applies only when listing recent orders. This goes beyond the individual parameter descriptions.

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 identifies a specific action ('Look up') and resource ('logged-in customer's orders'), and enumerates the returned data fields. It distinguishes this tool from cart/product/customer siblings by focusing on order status and order history.

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 gives clear usage context: use with a session_id from login, optionally pass an order_number for a single order, otherwise get recent orders. It does not explicitly name alternatives or exclusions, but this is not needed given the sibling set and the specificity of the tool.

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