Revert an applied pricing decision

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

Since no annotations are provided, the description carries full burden. It discloses that the tool changes prices (only with confirm), deletes custom rates, and restores prior rates from snapshot. It also mentions the API key requirement. No contradictions.

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 long, with no wasted words. Each sentence serves a purpose: stating core action and highlighting the confirm parameter and authentication requirement.

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?

Lacks description of the return value, which is important for understanding what the preview or result looks like. As a mutation tool with no output schema, the description should cover this but does not.

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 100%, and both parameters are well-described in the schema. The description adds minimal value: it clarifies that confirm must be true to actually delete and gives an example decision_id. This meets the baseline for high schema coverage.

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 reverts an applied pricing decision, specifying the actions: deletes custom rates and restores prior rates. It distinguishes from sibling tools like 'apply_decision' by focusing on the reversal 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 provides clear context: requires explicit confirm=true to execute, otherwise returns a preview. It also mentions the need for WHEELHOUSE_API_KEY. However, it does not specify when NOT to use the tool or list alternative tools.

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