图片镜像

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

Annotations already provide idempotentHint=true and destructiveHint=false, and the description adds useful return behavior: the flipped image is returned as base64 PNG along with metadata, and output_path only controls optional saving. It also clarifies that the result is still returned even when output_path is set. No contradiction with annotations.

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 leads with a one-sentence purpose, then presents parameters in a clean list and a short return note. Every sentence is functional and there is no filler.

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 simple, deterministic image transform, the description plus full schema and annotations covers accepted input forms, direction values, optional output path, and return format. An output schema exists, so return details need not be elaborated further.

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 all three parameters fully documented in the schema. The description repeats those parameter meanings but adds no new semantics 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?

States a specific operation: horizontally or vertically mirror-flip an image, explicitly mapping horizontal and vertical directions. This clearly distinguishes it from sibling image tools like rotate, crop, resize, and concat.

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 explicit when-to-use or when-not-to-use guidance is provided, nor are alternatives named. However, the operation is self-descriptive enough that an agent can infer to use this tool when the request is to mirror an image horizontally or vertically.

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