rotate_image_by_exif_data

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully mentions async 202 polling and that the output is saved under output_dir, which adds behavioral context. However, it omits important edge behaviors such as what happens when EXIF metadata is missing, file overwriting rules, or the exact return value, leaving transparency incomplete for a tool with no annotation support.

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 two sentences long and front-loads the core purpose, then adds key behavioral notes (async polling, output directory requirement). Every sentence contributes useful information without redundancy or fluff, achieving an ideal size 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?

The description covers the main behavior (rotation, output location) and a technical detail (async polling), but lacks information about return values and error cases, especially given there is no output schema. It is reasonably complete for a straightforward tool, but should have explained what the caller receives and how missing EXIF data is handled to be fully complete.

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 67%, with output_file_name lacking any schema description. The description reinforces the semantics of output_dir ('saves the rotated image under that directory') but adds little to file_path and nothing to output_file_name. It provides some value beyond the schema, but does not fully compensate for the undocumented optional parameter.

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 tool rotates a local image based on EXIF orientation metadata, using a specific verb ('rotate') and resource ('local image ... EXIF orientation metadata'). This distinguishes it from sibling tools like rotate_image and flip_image by naming the specific rotation trigger (EXIF) and the local input requirement.

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 provides clear context for when to use the tool: automatically rotating an image using EXIF orientation data. It also notes the requirement for output_dir. However, it does not explicitly state when not to use it (e.g., images without EXIF metadata) or name alternatives like rotate_image for manual rotation, so it falls short of full 'when/when-not/alternatives' guidance.

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