wafle_checkout_order_get

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

Annotations already identify the tool as read-only and idempotent. The description adds context about the order_id format but does not disclose any additional behavioral traits such as return structure or error conditions. This is acceptable given the annotations, but no extra transparency is provided.

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 two concise sentences with no filler. The primary action is front-loaded, and the parameter clarification is useful.

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 fetch tool given the annotations and full schema coverage. It clearly identifies the resource and parameter flexibility. It lacks a note on return values or differentiation from sibling order tools, but these are not essential for basic invocation.

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 covers both parameters with descriptions. The description enriches the order_id parameter by explaining that it accepts a numeric primary key or a public id with a specific pattern and where to find it (order detail page), going beyond the schema's example.

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 ('Fetch one order') and the resource ('wafle_orders'), making the tool's purpose unambiguous. It does not explicitly differentiate from similar siblings like wafle_orders_get, but the verb+resource is specific enough.

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 is needed and provides guidance on the order_id format. However, it does not explicitly state when to choose this tool over alternatives like wafle_checkout_orders_list or wafle_orders_get, nor does it mention any exclusions.

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