Delete WordPress Media Item

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

The description goes beyond the annotations by disclosing that deletion is always permanent, that force=false triggers a validation error, and by specifying the return shape. This adds valuable behavioral context that annotations alone do not provide, and it aligns with the destructiveHint=true annotation.

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?

The description is well-structured with a clear opening sentence, a concise Args section, and a Returns section. It is appropriately sized for a tool with three parameters and avoids unnecessary verbosity, front-loading the most critical information (permanence) first.

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?

Given the tool's simplicity and the absence of an output schema, the description is complete: it covers the action, the permanence constraint, parameter behavior, and the return value. The agent has all essential information to invoke the tool correctly and understand its consequences.

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 the baseline is 3. The description repeats the parameter details already present in the schema (id, force, response_format) and does not add new semantic meaning beyond what the schema provides. The additional note about force triggering an error is already in the schema description.

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?

The description clearly states 'Permanently delete a media item' with a specific verb and resource, and distinguishes itself from siblings by emphasizing the permanent nature of deletion (no trash support). This makes the tool's purpose unambiguous and unique among related media tools.

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?

The description provides clear context for when to use the tool (permanent deletion of media) and includes an important caveat that WP REST does not support trashing media. However, it does not explicitly name alternative tools or exclusions, though the warning about permanence implicitly guides usage.

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