wordpress_convert_to_webp

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the original image is replaced or a new file is created, permission requirements, or potential side effects. The tool's behavior beyond the basic conversion is entirely opaque.

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 extremely concise (5 words) but is under-specified. It front-loads the purpose but provides no additional value. A truly concise description would pack more information without unnecessary words.

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 the lack of annotations, output schema, and the presence of related sibling tools, the description is incomplete. It does not explain return values, error handling, or the implications of conversion (e.g., file size reduction, quality loss).

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 sole parameter 'mediaId' is not explained in the description. With 0% schema description coverage, the agent must infer its meaning from the name alone, which is insufficient for correct 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 'Convert image to WebP format' clearly states the action (convert) and the resource (image to WebP). It distinguishes from sibling tools like wordpress_bulk_optimize_images or wordpress_regenerate_thumbnails by specifying WebP conversion. However, it could be more explicit that it operates on WordPress media library images.

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. There is no mention of prerequisites (e.g., server support for WebP), no exclusions, and no comparison to related tools like bulk optimize or regenerate thumbnails.

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