lookup_order

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

With no annotations provided, the description carries the burden of disclosing behavior. It adds an authorization constraint ('when the customer is authorized') and mentions 'customer-safe' output, which is useful. However, it does not describe what happens for unauthorized access, nonexistent orders, or confirm explicitly that the operation is read-only.

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 concise and well-structured with Args and Returns sections. Every sentence adds value, and there is 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 two-parameter lookup with an existing output schema, the description covers the essential context: what is returned (customer-safe order status and delivery info), the authorization requirement, and parameter examples. It omits failure modes, but the output schema likely handles return details, and the tool is straightforward.

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 0%, so the description must compensate. It provides example formats (ORD-1002, CUS-002) and clarifies that customer_id is the 'authenticated customer identifier,' adding meaning beyond the bare schema. It could be more explicit about the relationship between the two parameters but is adequate.

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 the tool's function with the verb 'Look up' and the resource 'an order belonging to an authenticated customer.' It distinguishes itself from siblings like list_customer_orders (which lists multiple orders) and cancel_order (which modifies state) by focusing on a single order lookup.

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 is given for when to use this tool versus alternatives. The description does not mention that this is for retrieving a specific order by ID when the customer is known, nor does it reference sibling tools such as list_customer_orders for batch scenarios.

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