local_ydb_cleanup_storage

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

Annotations already indicate destructiveHint=true. The description adds detail that without confirm=true no deletion occurs, and only the explicitly supplied paths/volumes are removed. No contradiction with annotations.

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?

Two sentences that efficiently convey purpose and usage. First sentence states the core function, second provides critical guidance. No unnecessary words.

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 tool has 5 parameters, destructive nature, and no output schema, the description covers the essential aspects: when to use, how to trigger deletion, and safety. It could mention the format of the cleanup plan, but the plan-only mode is already indicated.

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 covers 100% of parameters with descriptions. The description enhances understanding by explaining the conditional behavior of confirm and the safety that only supplied items are deleted. This provides added value 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 tool deletes explicitly supplied storage paths or Docker volumes. It includes the verb 'Delete' and the resource ('local-ydb host paths or Docker volumes'), and distinguishes itself by mentioning inspection of local_ydb_storage_leftovers as a prerequisite, setting it apart from sibling tools like local_ydb_storage_leftovers.

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?

Explicitly states when to use the tool ('after inspecting local_ydb_storage_leftovers') and how to use it (with confirm=true for actual deletion, otherwise returns a plan). This provides clear context for correct invocation.

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