Bild bearbeiten

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

No annotations are provided, leaving the description to carry the full burden. It mentions using the WordPress Image Editor API but does not disclose side effects like overwriting original files, irreversibility, or impact on image sizes. The parameter 'applyToSizes' hints at behavior not covered in the description.

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 concise sentence that states the purpose and the key capability (using the WordPress API). Every word adds value, and it is efficiently front-loaded for quick understanding.

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?

The tool is complex with 6 parameters and nested objects, yet the description provides only a high-level overview. No output schema or annotations exist, so the description should explain typical usage, how parameters interact, and expected outcomes. It does not, leaving significant gaps for an agent.

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 100%, so the baseline is 3. The description adds no extra parameter semantics beyond what the schema already provides; it simply names the operations, which are already enumerated in the 'action' parameter.

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 tool edits an image and lists the specific operations (crop, rotate, flip), distinguishing it from siblings like image_get_details or image_update_meta. The verb 'Bearbeitet' (edits) and resource 'Bild' (image) are specific, and the enumeration of supported actions adds further clarity.

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 implies usage for image editing operations but does not explicitly state when to use this tool over alternatives such as image_update_meta or image_regenerate_thumbnails. It provides no exclusions or contextual guidance about prerequisites or fallback scenarios.

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