wordpress_delete_media

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly states that media cannot be trashed, implying permanent deletion, and that force must be true, while also noting the return value. It does not mention permissions or side effects, but the key destructive behavior is covered.

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 concise and well-structured with clear sections for summary, arguments, and return value. The main purpose is front-loaded, and there is no filler or redundant content.

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 simple two-parameter delete operation, the description adequately covers the action, the required force flag, and the return confirmation. Since an output schema exists, detailed return-value documentation is not necessary, and the description is sufficiently 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 0%, so the description must compensate. It explains media_id's role and, more importantly, clarifies the force parameter's requirement ('Must be true for media'), adding meaningful context beyond the raw schema types.

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 opens with 'Delete a WordPress media item,' a specific verb+resource statement that clearly identifies the tool's function. It also distinguishes it from sibling tools like wordpress_delete_post, wordpress_delete_page, and wordpress_delete_comment.

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 useful invocation context by stating that media cannot be trashed and force must be true. However, it does not explicitly explain when to prefer this tool over alternatives or mention any exclusions.

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