wafle_customers_segments_list

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 this is a safe, read-only operation. The description adds only the fact that segments are used in other contexts; it does not disclose additional behavioral traits such as response shape, pagination, or any limits. This is minimal beyond what annotations provide.

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 sentences, with the core purpose in the first sentence and an integration context in the second. Every word earns its place, no wasted 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 list tool with one fully described parameter and read-only annotations, the description is nearly complete. It explains what the tool returns (segments) and how they are used. The only minor gap is the lack of explicit response shape (e.g., whether it returns segment IDs or names), but since it's a list tool with no output schema, this is a small omission.

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 description coverage is 100% for the single `slug` parameter, which is fully described with format and example. The description itself doesn't add any further parameter semantics or syntax details, so the baseline of 3 applies.

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 uses the specific verb 'List' and clearly identifies the resource as 'customer segments configured for a store.' It also differentiates from siblings by noting these segments power the `segment=` filter in `wafle_customers_list` and audience exports, making its role distinct and unambiguous.

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 provides clear usage context by stating that segments power the `segment=` filter in `wafle_customers_list` and audience exports, implying when to use the tool (when a list of segment values is needed). It doesn't explicitly state exclusions or alternatives, but the cross-reference to the sibling tool gives the agent effective guidance.

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