Flip Image

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

No annotations are present, so the description must disclose behavioral implications. It states the action and endpoint but does not mention output behavior, file handling, overwrite semantics, or required permissions. As a result, the agent is left guessing about side effects and return values.

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 entire description is a single sentence that leads with the purpose, then lists inputs and options. It is appropriately sized and wastes no words.

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?

This is a relatively simple tool, but with no output schema and no annotations, the description should explain the result format and any side effects. It omits return value details and is vague about output file naming/destination. Given the tool's simplicity, the omissions are noticeable.

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 description names key parameters (image_file_path, orientation, request_doc_name, output path) and gives the valid orientation values, adding meaning beyond the raw schema. However, it uses the vague phrase 'output path' and does not clarify output_dir versus output_file_name. Schema coverage is 0%, so this partial compensation is helpful but incomplete.

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 opens with a specific verb and resource ('Flip an image horizontally or vertically'), clearly distinguishing it from sibling image tools like rotate_image or crop_image. The mention of the PDF4me endpoint is concrete but does not confuse the core function.

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 establishes a clear use case for flipping images either horizontally or vertically. It does not explicitly name alternative tools or state when not to use it, but the operation is self-evident among siblings. This meets the 'clear context, no exclusions' level.

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