flip_image

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states only the transformation and does not say whether the original image is modified, whether a new image is returned, or whether the operation is reversible. For a mutation-like image tool, this is a meaningful 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 front-loaded sentence with no filler: it gives the action, the target, and both direction options while adding the clarifying synonym 'mirror.' This is appropriately sized for the tool's complexity.

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 two-parameter tool with full schema documentation and an output schema, the description covers the core invocation semantics completely. It is only slightly thin on behavioral context such as in-place mutation versus returning a new image, but no required invocation detail is missing.

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%, with both image_id and direction already documented, including the enum and default. The description adds no new constraints, syntax details, or edge-case guidance beyond what the schema provides, so it earns the high-coverage baseline.

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 uses a specific verb ('Flip'), names the target resource ('the image'), and explicitly enumerates both supported directions. It clearly separates this operation from siblings like rotate_image or crop_image without needing to name them.

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 choose flip_image over sibling tools such as rotate_image, crop_image, or resize_image. There are also no prerequisites, exclusions, or contextual hints beyond the implied meaning of 'flip.'

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