wordpress_convert_to_webp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'Convert image to WebP format' without explaining whether the original file is replaced, whether a new media item is created, whether the operation is reversible, or what side effects occur. This is a significant gap for a mutation tool.

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 sentence with no filler words. It gets straight to the point. Every word is necessary, and there is no redundant information.

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 tool with one parameter, no output schema, and no annotations, the description is still incomplete. It doesn't state what the result of the conversion is (e.g., success message, new URL) or describe any side effects. Users would need to guess whether the original media is replaced or a new file is created. This falls short of a minimum viable description.

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?

The input schema exposes one required parameter, mediaId (number), but the description does not explain what mediaId is or how it relates to the conversion. Schema coverage is 0%, and the description only says 'image' without connecting it to the parameter. The name mediaId is somewhat self-explanatory, but the description adds no explicit meaning beyond the schema.

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 uses a specific verb 'Convert' and resource 'image', and specifies the target format 'WebP'. It clearly states the tool's function. However, it doesn't explicitly differentiate from sibling tools like wordpress_bulk_optimize_images, which may also involve WebP conversion, so it loses a point for lacking explicit distinction.

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. It doesn't mention prerequisites (e.g., supported input formats), whether it's for single-image conversion, or any reference to other tools. There is no 'use this when...' or exclusionary context.

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