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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat this. The description provides no additional side-effect information, but none is required given the annotations.

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 short and to the point, but it contains a slight redundancy: 'Returns the details of a given order.' is repeated in the 'Guidance' clause. This does not harm clarity but could be trimmed.

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 description is sufficient for a simple getter operation. There is no output schema, but the tool name and parameter indicate it returns order details, which is typical for such getters in this API family.

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 schema fully describes order_id as the unique ID of the order, and the description echoes that. Since the schema coverage is 100% and the description adds no extra semantic detail, the baseline of 3 is appropriate.

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?

Clearly states the tool returns details of a specific order identified by order_id. This distinguishes it from sibling tools like shop_list_orders, which list multiple orders, and other getters for different resources (products, customers, etc.).

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 when a single order's details are needed by ID. While it doesn't explicitly contrast with alternatives such as shop_list_orders, the function name and parameter make the appropriate context obvious.

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