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

Annotations only declare destructive/non-idempotent. The description goes much further: it enumerates exactly what is destroyed (workloads plus data in that deployment's database and volumes, deletion of the installation) and what is retained (settings, secrets, images, release history, other installations, shared add-ons), and discloses async semantics ('Accepted is not done') plus conflict-refusal conditions.

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?

Front-loaded with the core action and consequence, and nearly every sentence carries content (destroyed vs kept, async state, refusals, alternatives). It is long, but the density is earned rather than padded; the parenthetical tool references are the only slight friction.

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, no-output-schema mutation, the description covers the full operational picture: destruction scope, retained resources, async completion state and how to observe it, failure reason, refusal cases, and the correct sibling for each alternative goal.

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%, so baseline is 3, but the description adds real meaning beyond the schema: the namespace/stack_name split is framed as deployment identity (one application can be deployed twice on one cluster), and it explains that a deploy-wizard deployment is named by stack_name with no installation.

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?

States a precise verb+resource+scope: remove ONE deployment from one cluster/namespace while the Application and its other deployments stay. It explicitly delimits against siblings (park_application_deployment, delete_application), so an agent can distinguish it without opening schemas.

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?

Gives a prerequisite (use list_application_installations first to find cluster and namespace), names the two alternatives with the conditions that select them ('stop it for a while without losing anything, use park...', 'delete the Application everywhere, delete_application'), and covers the deploy-wizard naming case.

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