rotate_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies mutation ('rotate the image') but does not state whether the operation modifies the image in place, returns a new image, or is reversible. There is no mention of side effects, permissions, or limitations, which is a significant gap for a mutation tool.

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 a single, concise sentence that directly states the action and the allowable degrees. It is front-loaded with the core verb and resource, with zero wasted words. This is an appropriate length for a simple operation.

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 tool is simple, and the schema plus output schema cover the parameters and return values. However, without annotations, the description does not clarify whether the rotation is destructive or reversible, nor does it provide any usage context or alternatives. While the description is minimally sufficient for a basic operation, it leaves behavioral questions unanswered, making it only partially 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 description coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides; it merely reiterates the angle values that are already enumerated in the schema. Since the schema fully documents both parameters, the description does not need to compensate, but it also does not add value.

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 states a specific verb ('rotate') and resource ('the image') along with the allowed angles (90, 180, 270), making the action unambiguous. It clearly distinguishes from siblings like flip_image (which flips rather than rotates) and resize/crop, so an agent can select it correctly without opening the schema.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions (e.g., when flip_image might be preferred, or whether rotation is in-place or creates a new image). This is a pure functional statement with no contextual usage information.

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