wafle_pricing_rules_create

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

Annotations only provide idempotentHint=false. The description adds behavioral context such as fixed_price 'overrides multiplier' and the warning about production impact, but doesn't disclose other side effects like whether an existing rule is overwritten or what permissions are required.

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 well-structured with a bulleted list and a clear cautionary note, front-loading the core purpose. Each sentence adds information without redundancy.

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 description covers the main rule types, value formats, and a preview step, but omits that `target` is effectively required for `category_markup` and `fixed_price`, and doesn't mention the output of creation. Still, it's fairly complete given the schema and annotation coverage.

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 description thoroughly explains the `value` parameter for each type, with an example for multiplier, and clarifies the meaning of each `type` enum value. This compensates for the 50% schema coverage and adds significant meaning beyond the input schema.

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 opens with 'Create a new pricing rule', a specific verb+resource, and then enumerates four rule types with their effects, clearly distinguishing this create operation from update/delete/list siblings. It also provides concrete examples like '2.2 = +120% on every base price'.

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?

It explicitly instructs to 'Always preview with wafle_pricing_compute_preview before committing rules in production', providing a clear prerequisite and companion tool. However, it doesn't explicitly state when to use update/delete instead, relying on the tool name for that distinction.

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