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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description still adds real value beyond that: it names the exact resource removed (ankra-demo-pr-<n> namespace on the staging cluster) and the second effect of marking the tracking record destroyed, which tells the agent the operation has a persistent bookkeeping consequence. It stops short of noting reversibility or failure modes, so not a 5.

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, no filler, and the destructive effect plus resource is front-loaded before the parameter rule. Every clause earns its place.

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?

With no output schema, the description usefully describes the resulting state (namespace gone, tracking record marked destroyed), which is what an agent needs to reason about afterward. It leaves out whether the demo can be re-created afterward and whether the call is safe to retry, minor gaps for a two-parameter teardown tool.

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% and both parameter descriptions already state the namespace format and the 'optional if the other is given' relationship. The closing sentence 'Provide either the namespace or the pr_number' restates that same either/or rule without adding format, resolution precedence, or what happens if both are supplied. Baseline 3 is correct when the schema does the work.

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 specific verb (tear down), a specific resource (a PR demo deployed by deploy_pr_demo), and the exact side effects (delete ankra-demo-pr-<n> namespace, mark tracking record destroyed). It explicitly names the sibling create-side tool, so an agent can place it precisely among deploy_pr_demo, redeploy_demo, and inspect_demo.

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?

Usage is implied: this undoes a demo created by deploy_pr_demo, which gives clear context for when to reach for it. However it never states when NOT to use it (e.g., versus redeploy_demo or destroy_playground) and gives no preconditions such as cluster availability or who may stop a demo. Adequate but gaps remain.

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