wordpress_delete_media

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

The description implies a destructive operation but lacks details such as whether force=true is required for permanent deletion, permission requirements, or side effects. Without annotations, the agent is left unaware of important behavioral traits.

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 a single short sentence, which is concise but at the cost of omitting essential information. It fails to provide a complete picture, thus not earning its place efficiently.

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 no output schema, no annotations, and two unparameterized params, the description is severely incomplete. It does not specify return values, error cases, or behavioral nuances, leaving the agent poorly informed.

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 the description does not explain the meaning or role of mediaId or force. The force parameter's boolean nature is critical but completely undefined, making it difficult for an agent to invoke correctly.

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 'Delete a media file from library' clearly states the action (delete) and the resource (media file from library). It distinguishes from siblings like upload_media, update_media, and bulk_delete_media.

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 no guidance on when to use this tool versus alternatives like wordpress_bulk_delete_media, or how the force parameter affects behavior (e.g., trash vs permanent delete). No context on prerequisites or best practices.

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