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

Annotations already mark this destructive and non-idempotent, but the description adds genuinely new behavior: the member-emptiness precondition, the refusal failure mode, and the destruction scope (the mesh record and its certificate authority). That is exactly the context annotations do not carry.

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?

Three short sentences, front-loaded with the action, then the prerequisite, then the destruction scope. No filler and nothing buried.

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 single-parameter delete with no output schema, everything an agent needs is present: what it deletes, what must happen first, what happens on violation, and what is irreversibly lost.

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% for the single mesh_id parameter ('The mesh UUID to delete'), so the schema already does the work. The description adds no format, lookup, or sourcing detail beyond it; baseline 3 is appropriate.

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?

'Delete a cluster mesh' is a precise verb+resource, and the description immediately differentiates it from the sibling remove_cluster_from_mesh and create_cluster_mesh by stating what it removes and what it requires. An agent can route to it without opening the schema.

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?

It gives an explicit precondition ('Remove its members first with remove_cluster_from_mesh') and the consequence of ignoring it ('deleting a mesh that still has members is refused'). It names the alternative tool by name and the condition that selects it.

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