wp_delete_media

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

With no annotations provided, the description carries the behavioral burden. It clearly signals that deletion is permanent and discloses a non-obvious WordPress requirement: 'force:true' is required. It could add more side-effect detail, but the core destructive behavior is transparent.

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 sentences with no filler. The primary action is front-loaded, and the second sentence adds a necessary requirement without redundancy.

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 small deletion tool with no output schema, the description covers the essential behavior: permanent removal, required force flag, and a previewable dry_run from the schema. It could mention irreversibility side effects or return format, but the tool is simple enough that the current description is nearly complete.

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 only 33%, so the description must compensate. It adds meaningful context for the force parameter by explaining WordPress requires it, and the phrase 'media attachment' helps clarify that id identifies the attachment. It does not fully describe id or force beyond the schema, but it provides enough to guide invocation.

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 states a specific verb and resource: 'Permanently delete a media attachment.' The word 'permanently' adds important scope and distinguishes this irreversible delete operation from update/get/list media tools among the siblings.

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 purpose statement implies when to use the tool: when a media attachment must be permanently removed. However, it does not explicitly name alternatives or exclusions, such as distinguishing this from wp_delete_post or wp_update_media.

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