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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavior: the blast radius spans every revision plus the pointer memory, the effect is permanent, and a confirm-name guard is enforced. It does not say what happens on a mismatched confirm value or whether other references to the artifact break.

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?

Four short fragments, front-loaded with the destructive scope before the routing hint. Nothing is repeated from the schema or annotations and no sentence is filler.

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 and annotation coverage of its safety profile, the description supplies the essential pieces: cascade scope, irreversibility, and the confirm guard. The only gaps are error behavior on a name mismatch and any permission requirements.

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 only 50% — confirm is documented but artifact_id has no description. The description compensates by stating the equality constraint ('confirm must equal the artifact name'), which is stricter than the schema's 'The artifact name' and tells the agent it cannot be an arbitrary string. artifact_id's meaning is left to inference from the tool name.

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 and resource ('Delete an artifact') plus the scope of deletion ('every revision and its pointer memory'). It explicitly distinguishes itself from the sibling memory_delete, so an agent can choose between them without opening either 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?

Gives a clear routing rule: memory_delete refuses a pointer, so use this tool for pointer artifacts. That names the alternative and the condition that selects it. It stops short of stating when deletion should be avoided or what prerequisites (ownership/permissions) apply.

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