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

With no annotations, the description carries the full burden, and it does disclose two real traits: it runs in the browser and it consumes credits that are covered by welcome credits / Day Pass. It also discloses an English-only language restriction. However, it never explains the mechanic that matters most for a zero-parameter tool — how the image is supplied (upload vs. workspace selection) or what happens on an unsupported/failed extraction.

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 purpose is correctly front-loaded in the first clause, but three of the four sentences are duplicated pricing/credit boilerplate that is already served by the mioffice_pricing_info sibling and adds nothing about invoking this tool. There is also a doubled period after 'editing.' — a small sign of unedited text.

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-param, no-annotation, no-output-schema tool, the description does identify the transformation and the deliverable ('copy the result for editing'), which is enough to know roughly what comes back. It is still incomplete on the input handoff — nothing says how an agent with no parameters actually gets an image into it — which is the one thing an agent must know before calling.

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 tool takes zero parameters (empty properties object), so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter documentation is expected or missing here.

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?

"Handwriting to Text — Extract English text from an uploaded handwriting image" names a specific transformation, the input medium, and the output type. The handwriting qualifier implicitly separates it from the OCR-style scanner siblings (mio_scanner_document, mio_scanner_receipt) and from mio_ai_transcriber, though it never names an alternative 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?

There is no statement of when to choose this over mio_scanner_document, mio_scanner_book, or mio_pdf_to_text, and no exclusion or prerequisite guidance. The only implicit signal is 'uploaded handwriting image', which an agent must infer means handwritten (not printed) input. The remaining sentences are about billing, not usage.

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