wafle_customers_orders

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the 'single customer' scope and email-based identification, but does not disclose pagination behavior, sorting, or return structure. With annotations covering safety, this is adequate but not rich.

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?

One clear, front-loaded sentence. No filler or repetition. Every word earns its place.

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 tool has four parameters and no output schema. The description is sufficient for a simple list operation, but lacks details about pagination behavior or the structure of returned orders. Given annotations and schema, it is minimally adequate but not fully complete.

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 75% with descriptions for page, slug, and per_page. The description only reinforces that email is the customer identifier, which adds minimal value beyond the schema. It does not explain how slug, page, and per_page interact.

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 'List the orders of a single customer (by email)' clearly states the verb, resource, and scope. It distinguishes from sibling tools like wafle_orders_list (which likely lists all orders) and wafle_customers_get (customer data).

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?

Implies usage when you have a customer email and need their order history. It does not explicitly mention alternatives or exclusions, but the 'single customer (by email)' context provides clear guidance. No exclusions given, so it falls short of a 5.

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