manage_image

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

Annotations only include a title with no readOnly or destructive hints, so the description carries the full burden. It does not disclose whether the tool mutates the presentation, overwrites files, applies temporary or permanent effects, or what side effects the enhancement operations have.

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 redundant wording, and it is front-loaded with the tool's general purpose. It is concise in structure, even though that brevity fails to compensate for missing substantive detail.

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 17 parameters, 3 required fields, no schema descriptions, and rich sibling differentiation needs, the description is severely incomplete. It does not explain valid operations, image source handling, coordinate and dimension semantics, or enhancement options, making correct invocation nearly impossible.

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% across 17 parameters, and the description mentions none of them. The agent gets no help understanding critical parameters like operation, image_source, source_type, filter_type, or enhancement_style.

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 says the tool is for 'adding and enhancing images,' which gives a general sense of the operation, but 'unified image management' is a broad, imprecise framing. It does not clearly distinguish this tool from sibling tools like add_image_from_dial_url or apply_picture_effects.

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 about when to use manage_image instead of its siblings. There are no conditions, exclusions, or alternative tool references, leaving the agent to infer usage solely from the vague description.

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