get_order

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It only states the action (retrieve), implying a read operation, but does not confirm idempotency, error handling, or what happens if the order is not found.

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 very short, but the prefix 'post-order:' is unclear and may be confusing. It would be better without it. The core message is concise but could be structured more clearly.

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 description should explain what is returned (e.g., order details). It does not cover this, nor does it address common error scenarios. The description is too minimal for a tool with two parameters and no output definition.

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?

The description adds meaning to both parameters: 'number' is the order number, and 'order_token' is for guest checkout. Since the schema has 0% description coverage, this compensates well. However, it does not specify the format or that order_token is optional.

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 action (retrieve an order), the resource (order), and the key identifier (by number). It also distinguishes from sibling tools that deal with products and taxonomies. The mention of 'guest checkout' adds specificity.

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 a hint about when to use the order_token parameter (guest checkout), but it does not provide explicit guidance on when to use this tool versus alternatives like get_product. No exclusions or when-not-to-use are mentioned.

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