wafle_customers_get

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows it is a safe read. The description adds value by disclosing the return contents (lifetime value, order count, last seen, top SKUs), providing behavioral context beyond 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 a single, well-structured sentence that front-loads the core action and resource, followed by a concise list of return stats. Every word adds value with no redundancy or filler.

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?

Given the tool's simplicity (2 params, no output schema, read-only annotations), the description adequately covers what it does and what it returns. It lists the aggregated stats, which is sufficient for an agent to know the expected output, though it omits details like error conditions or response format.

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%: the slug parameter is well-described, while email has only a format. The description clarifies that email is the lookup key, but does not add detail for slug or further explain parameter meaning. It partially compensates for the email gap but remains moderate.

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 tool 'Fetch a single customer profile by email', specifying the verb (fetch), resource (customer profile), and unique access method (by email). It also lists the returned stats, distinguishing it from sibling tools like wafle_customers_list and wafle_customers_orders.

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 for retrieving a specific customer, but it does not explicitly contrast with alternatives or provide when-to-use vs. when-not-to-use guidance. Sibling tools like wafle_customers_list exist, and the description does not mention when to choose this over them.

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