wafle_orders_get

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

The annotations already declare readOnlyHint and idempotentHint, but the description adds meaningful context by enumerating the returned data categories (customer, items, totals, gateway info, status, shipment data, timeline reference). This goes beyond the structured annotations and helps the agent understand the tool's output.

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 a single, front-loaded sentence that states the action first and then lists the returned fields in a compact, readable list. No superfluous words or repetitive content.

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 get-by-id operation with readOnly and idempotent annotations, the description covers the primary behavior and key return fields. It does not mention error conditions, authorization requirements, or how it relates to sibling order tools, but these are not critical for such a straightforward operation.

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 50%: slug has a description, but order_id does not. The description implies that order_id is the identifier used to fetch a single order, providing some semantic value, but it does not elaborate on the id's format or any additional constraints, leaving order_id partially under-explained.

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 states a clear action ('Fetch a single order by id') and the resource (order), making the purpose readily apparent. However, it does not distinguish itself from the sibling tool wafle_checkout_order_get, which likely serves a similar function, so it doesn't fully differentiate.

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 guidance is given on when to use this tool versus alternatives like wafle_checkout_order_get, wafle_orders_list, or wafle_orders_timeline. The description only states what the tool does, leaving the agent to infer usage context from the name and schema.

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