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

Without annotations, the description carries the burden of behavioral disclosure. It only notes 'Runs in the browser' and credit/pricing details, but does not explain side effects, whether the original image is preserved, how the rotation angle is specified, or any limitations. This is minimal and under-specified.

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 front-loaded with the core purpose ('Rotate and flip images') followed by a concise note about credits and pricing. The pricing details add length but are relevant for agent decision-making regarding access. It is not overly verbose.

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?

With no annotations, no output schema, and no parameters, the description must provide complete context. It fails to explain how to specify rotation angle or flip direction, whether an input image is provided separately, or what the output looks like. The pricing info, while useful, does not compensate for these operational gaps.

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 input schema has zero parameters, so schema coverage is 100% and there is nothing to document. The baseline for 0-param tools is 4, and the description does not need to add parameter details. It does not confuse with pseudo-parameters.

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's function: 'Rotate and flip images.' This provides a specific verb (rotate/flip) and resource (images), and distinguishes it from video rotation tools by explicitly naming images.

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?

Usage context is implicit from the name and description—use when you need to rotate or flip an image. However, there is no explicit guidance on when to choose this tool over alternatives like mio_image_crop or mio_image_resize, nor any exclusions or prerequisites.

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