Delete a snippet

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds value beyond them by stressing 'Permanently' (irreversibility) and disclosing the required confirmation token 'confirm:"delete"' — a mutation guard the schema does not encode (confirm is only typed as a plain string with no enum).

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 short, front-loaded sentences with zero filler: the action and permanence come first, then the confirmation requirement. Every sentence 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?

For a destructive two-parameter tool with no output schema, the description covers the essential behavior (permanent removal, mandatory confirm token). It omits only secondary details such as required permissions and what happens on a missing/incorrect confirm value.

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 description coverage is 0% and there is no enum on 'confirm', so the description must carry parameter meaning — and it does, specifying the exact literal value 'delete' required for confirmation. The remaining 'id' parameter is self-evident as the snippet identifier, so this is only a minor gap.

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 ('Permanently remove') and resource ('a stored snippet'), clearly distinguishable from sibling tools like wp_content_delete, wp_snippet_save, and wp_snippet_run. An agent can tell exactly what this does 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?

Usage is implied ('Permanently remove a stored snippet') but there is no explicit when-to-use, when-not, or alternative guidance. It does not tell the agent how to choose this over wp_snippet_save (to overwrite) or that deletion is irreversible with no undo path.

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