revert_calibration_recommendations

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

With no annotations, the description must carry the behavioral load, and it does disclose the concrete artifact affected (applied_settings.json) and the end state (resolvers back to defaults). It omits reversibility, whether prior settings are recoverable, confirmation requirements, and tier-gating enforcement details, while spending most of its length on an unrelated marketing pitch.

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 one useful sentence is correctly front-loaded, but it is followed by three sentences of pricing advertisement and a tracking URL that consume roughly three quarters of the text. That material does not help an agent invoke the tool and should not be in a tool description.

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 zero-parameter, unannotated, no-output-schema destructive operation, an agent needs to know the destructive scope and whether the action can be undone; the description implies irreversible deletion of a settings file but never states it, and pads the remainder with promotional copy instead of operational context.

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 tool takes zero parameters, so the baseline is 4; there is nothing about argument semantics the description could or should add. The schema coverage being 100% with an empty properties object confirms no gap exists.

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 first sentence gives a concrete verb and resource — delete applied_settings.json and revert all resolvers to defaults — which is unambiguous. It does not, however, distinguish this tool from the calibration siblings (apply_calibration_recommendations, get_calibration_health_recommendations), and the three trailing sentences describe Pro-tier features rather than this tool's purpose.

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?

There is no statement of when to revert versus when to apply or assess calibration, even though apply_calibration_recommendations and assess_calibration_status sit in the same sibling set. The only usage signal is an incidental 'Requires Kiln Pro' buried in an upsell paragraph.

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