rotate_image

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

Since no annotations are provided, the description must disclose behavioral traits itself. It does mention async 202 polling and that the rotated image is saved to disk, which are useful. However, it omits whether the source file is modified, overwrite behavior, and authentication or rate-limit requirements.

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 with no filler. The first sentence front-loads the core action and API, followed by a concise list of supported features and output behavior.

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 6-parameter tool with no annotations or output schema, the description covers the purpose, the async behavior, and the disk-saving behavior. However, it is incomplete because it does not mention the return value, error handling, or any prerequisites such as file format support.

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 67%, with descriptions for file_path, rotation_angle, background_color, and proportionate_resize. The description adds some context by noting 'optional output directory and file name' for the undocumented output_dir and output_file_name parameters, but it does not provide deeper parameter-level semantics beyond what the schema already includes.

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 gives the specific action 'Rotate a local image' using the PDF4me RotateImage API, which identifies the verb and resource unambiguously. However, it does not explicitly distinguish this from sibling tools like rotate_image_by_exif_data, so it rates a 4 rather than 5.

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 no guidance on when to use this tool versus alternatives such as rotate_image_by_exif_data, resize_image, or flip_image. The only usage signal is the phrase 'Rotate a local image,' which implies the purpose but gives no exclusion criteria or alternative pointers.

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