wafle_pricing_rules_delete

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

The annotation already provides destructiveHint=true, and the description adds 'Irreversible' and 'confirm before calling,' which reinforces permanence and adds an actionable safeguard. This provides context beyond the annotation without contradicting it.

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 short sentences, with the action front-loaded and the critical warning in the second sentence. No waste.

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 delete tool with annotations and two parameters, this is mostly adequate, but it lacks details like expected return values, behavior if the rule does not exist, and the role of the slug parameter in scoping. The presence of idempotentHint and destructiveHint helps, but the description itself could include a note that deletion is scoped by store slug.

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 says 'by id' but does not explicitly map which parameter (rule_id) is the identifier; the schema only describes slug, leaving rule_id without description. Since the description adds no additional meaning beyond the schema, it fails to compensate for the undocumented rule_id parameter.

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 'Delete' with the resource 'pricing rule by id', making the tool's purpose immediately obvious. The name and sibling tools (create/update/list) further distinguish it as the delete operation.

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 warns 'Irreversible — confirm before calling,' which is a relevant usage caution, but it does not explicitly state when to prefer this tool over alternatives like update or list. There is no guidance about prerequisites or using list to find rule IDs first.

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