flip_image

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the flip modifies the image in-place, returns a new image, or affects the undo stack. This is a significant gap for a mutation tool, as the agent cannot infer side effects or required permissions.

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 that conveys the essential action without excess words. Every part is meaningful, and it is appropriately sized for the tool's simplicity.

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 tool's simplicity and the presence of an output schema, the description is reasonably complete for basic usage. However, it lacks details on side effects (e.g., in-place modification vs. new image) and any prerequisites (e.g., image must be open), which are important for an agent to use it correctly and safely.

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 coverage is 0%, so the description must compensate. It mentions 'HORIZONTAL or VERTICAL', which suggests possible values for 'direction', but does not specify exact string formats, case sensitivity, or default behavior. The 'image_id' parameter is left entirely to the schema, so the description adds only partial value.

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') and resource ('an image'), and clarifies the two possible axes (HORIZONTAL or VERTICAL). This clearly distinguishes it from the sibling tool 'rotate_image' which performs rotation, not mirroring.

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 flipping an image, but does not explicitly state when to prefer this over alternatives or provide any exclusions. No comparison to sibling tools like rotate_image is given, leaving some ambiguity for the agent.

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