clear_plans

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

With no annotations provided, the description carries the full burden. It discloses the safety gate (confirm=true must be set to delete), which is a behavioral trait. However, it does not mention irreversibility or side effects, leaving some transparency gaps.

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 a single sentence that is front-loaded with the action and resource, immediately followed by the key usage condition. No extraneous words—every phrase is purposeful.

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 simplicity of the tool (a delete action with three parameters, no output schema), the description is fairly complete. It covers what is deleted, the options, and the safety gate. It could mention irretrievability, but overall it provides enough context for effective use.

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 schema provides 100% coverage for all three parameters. The description adds marginal value by reinforcing the confirm requirement and listing target options, but does not explain the optional modelName parameter beyond the 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 clearly states the action ('delete') and resource ('plan files'), and enumerates the specific options for the target parameter ('all', 'round1', 'round2', 'final'). This distinguishes it from sibling tools like export_plans or final_plan.

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 the critical requirement 'Must set confirm=true', which is a key usage condition. However, it does not mention when to use this tool over alternatives or provide exclusion criteria, though the sibling tools provide context.

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