wordpress_convert_to_webp

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

No annotations are provided, so the description carries full burden. 'Convert image to WebP format' implies a mutation operation but doesn't disclose behavioral traits like whether it overwrites the original, creates a new file, requires specific permissions, has rate limits, or returns a result. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero waste. It's appropriately sized for a simple tool and front-loaded with the core action, though it could benefit from additional context.

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 a mutation tool with no annotations, 0% schema coverage, no output schema, and 1 parameter, the description is incomplete. It lacks details on behavior, parameters, return values, and usage context, making it inadequate for an agent to invoke the tool correctly without guesswork.

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 adds no parameter information beyond what the schema provides. The single parameter 'mediaId' is undocumented in both schema and description, leaving its meaning (e.g., WordPress media ID) unclear. The description doesn't compensate for the coverage gap.

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 'Convert image to WebP format' clearly states the action (convert) and target (image), but it's vague about scope and doesn't distinguish from sibling tools like 'wordpress_bulk_optimize_images' or 'wordpress_update_media'. It specifies the format but not what happens to the original image or where the conversion occurs.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'wordpress_bulk_optimize_images' (which might include WebP conversion) and 'wordpress_update_media', the description lacks context for choosing this specific tool, prerequisites, or exclusions.

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