local_ydb_destroy_stack

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

Annotations mark the tool as destructive (destructiveHint: true), and the description expands on that by enumerating exactly what is removed: tenant metadata, containers, network, storage, and optional host paths. This adds useful context beyond the annotation, though it does not detail all potential side effects.

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, well-structured sentence of 20 words. It front-loads the verb 'Remove' and lists resources concisely. No extraneous information.

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 destructive tool with no output schema, the description covers the scope of what is removed, but it omits mention of the critical confirm parameter that controls execution vs. dry-run. Given the destructive nature, this is a notable gap.

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?

Parameter schema coverage is 100%, so the description is not required to detail each parameter. However, it does hint at optional cleanup via 'with optional host-path cleanup,' which maps to the removeBindMountPath, removeAuthArtifacts, and removeDumpHostPath parameters. This adds marginal value over 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 ('Remove') and specifies the resources affected: tenant metadata, containers, network, storage for a profile. This distinguishes it from sibling tools like local_ydb_cleanup_storage (which only removes storage leftovers) and local_ydb_remove_dynamic_nodes.

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 implies the tool is for full teardown of a profile's resources, but it does not explicitly state when to use this tool versus its more specific siblings (e.g., local_ydb_cleanup_storage, local_ydb_remove_dynamic_nodes). No exclusion or guidance on alternatives is provided.

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