flip

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly states the source is unchanged and that a new file is created, which is crucial non-destructive behavior. It also mentions the return value (output path and axis used). It does not cover error handling or format constraints, but for a simple flip operation, these disclosures are sufficient.

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 exactly two sentences, front-loaded with the primary purpose and key guarantee (new file, source unchanged). It covers the axis parameter and the return value in a compact, scannable format. Every word adds value—there is no fluff or redundancy.

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 straightforward flip tool, the description is complete: it explains the operation, the source preservation, and what is returned. It does not mention supported image formats, file size limits, or error behavior, but these are minor for a tool of this complexity. The schema covers all parameters fully, and the description fills in the behavioral return value, making it sufficient for correct usage.

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 schema has 100% coverage with clear descriptions for each parameter (path, out, axis), including the default for axis. The description adds no new parameter-specific information—it even repeats the axis semantics from the schema. Since coverage is high, the baseline of 3 applies; the description provides no additional semantic value beyond the schema.

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 ('Mirror an image') and the key outcome ('write it to a NEW file (source unchanged)'). It distinguishes itself from sibling tools like rotate or resize by explicitly naming the operation and the axis options. This leaves no ambiguity about what the tool does.

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 when to use the tool (whenever an image needs to be mirrored) but does not explicitly contrast it with alternatives like rotate or crop. It provides no exclusionary guidance (e.g., 'use this for flips, not rotations'), relying on the tool name and operation to convey intent. This is acceptable but not proactive in steering the agent.

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