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

With no annotations, the description carries the full burden. It usefully discloses that the tool "Runs in the browser" and that it consumes signup credits or the Day Pass, which is real behavioral context, but it never states what a call actually returns or whether the original file is preserved.

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 first sentence is well front-loaded and complete, but more than half the text is promotional boilerplate about welcome credits, Day Passes, workspace groups, and a pricing URL that does not help an agent invoke the tool. A stray double period ("share..") also signals unedited copy.

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 zero-parameter tool with no annotations and no output schema, the description should clarify the invocation model (does the call open a browser flow, return a job, or produce a file handle). It instead spends its remaining budget on pricing, leaving the mechanics of the call unexplained.

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 schema has zero properties, so the baseline would be 4, but the description's "Choose the turn" implies an angle input that does not exist in the schema. An agent is left unsure whether the rotation value is supplied elsewhere (e.g., a browser UI), which is a genuine ambiguity rather than added clarity.

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?

"Rotate all PDF pages by 90, 180 or 270 degrees" gives a specific verb, resource, scope (all pages) and the allowed angle set. The PDF resource noun implicitly separates it from mio_image_rotate and mio_video_rotate, though no sibling is named explicitly.

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?

"Choose the turn, process your document, and download a PDF copy to check and share" sketches a basic workflow, but there is no statement of when to prefer this over mio_pdf_editor, mio_pdf_to_jpg, or other PDF siblings, and no prerequisites or exclusions.

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