wafle_pricing_rules_list

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safe-read profile is established. The description adds value by listing the categories of rules returned and emphasizing the composability aspect, which is useful 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?

Two sentences, no fluff, front-loaded with purpose and rule types, followed by a practical usage note. 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?

Given the single parameter, strong annotations, and list-oriented nature, the description is complete: it states what's listed, when to use it, and why. The absence of an output schema is acceptable because the returned items are clearly implied as the pricing rules themselves.

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?

The only parameter 'slug' is fully described in the input schema with pattern and examples, giving 100% schema coverage. The description itself does not add parameter syntax or additional meaning, so it meets the baseline for schema-covered params.

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 a specific verb ('List') and identifies the resource ('dynamic pricing rules of a store') while enumerating rule types (catalog-wide multipliers, category markups, etc.). This clearly distinguishes from sibling tools like wafle_pricing_rules_create, update, and delete.

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 explicitly states when to use it ('Use before editing') and explains why ('pricing rules compose, so you need to know what's already there'). This gives clear contextual guidance and implies alternatives (editing tools).

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