wordpress_bulk_optimize_images

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Bulk optimize' implies a potentially resource-intensive write operation affecting multiple images, but the description doesn't mention performance impact, permissions required, whether it's reversible, or what happens to original files. 'Compress all images' suggests comprehensive coverage but lacks details on scope or exclusions.

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 (three words in parentheses) and front-loaded with the essential action. Every word earns its place: 'bulk' indicates scale, 'optimize' specifies the action, and 'compress all images' clarifies the method and scope. No wasted words or 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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'optimize' entails technically, what compression settings are used, whether quality loss occurs, how progress is reported, or what the return value contains. The agent lacks critical information to use this tool effectively despite its zero-parameter simplicity.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the input structure. The description doesn't need to explain parameters, and it appropriately doesn't attempt to. A baseline of 4 is appropriate for zero-parameter tools where the schema handles all parameter documentation.

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 clearly states the action ('bulk optimize images') and resource ('images'), with 'compress all images' providing additional specificity about the optimization method. It distinguishes from siblings like 'wordpress_convert_to_webp' (different format conversion) and 'wordpress_regenerate_thumbnails' (different image processing), but doesn't explicitly contrast with them in the text.

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_convert_to_webp' or 'wordpress_regenerate_thumbnails'. It doesn't mention prerequisites, timing considerations, or what 'bulk' entails in practice. The agent must infer usage from the name alone.

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