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

No annotations exist, so the description carries the full burden. It does disclose useful behavioral facts (browser execution, 20-page scanned-document cap, English-only automatic OCR) but says nothing about how the PDF is supplied, where the resulting TXT files go, or what failure looks like at the page limit.

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?

Purpose and limits are front-loaded well, but half the text is pricing boilerplate ('no per-workspace subscription', 'See mioffice.ai/pricing') that duplicates the dedicated mioffice_pricing_info tool and dilutes the operational content. There is also a stray double period.

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, no-output-schema, no-annotation tool, the description covers the essentials: what is produced (TXT files), the browser execution model, and the hard limits. The remaining gap is invocation mechanics — how the input PDF is provided — but the 'Runs in the browser' hint plus the mioffice_open_tool sibling largely fills that.

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 declares zero properties, so there are no parameters whose semantics need explaining — baseline 4 per the zero-parameter rule. The description adds the operational limits an agent would want before calling, though it never explains how a file reaches a parameterless tool.

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 first sentence names a specific verb and resource plus the output artifact ('Extract PDF text into separate TXT files'), which cleanly separates it from mio_pdf_to_doc and mio_pdf_to_xlsx. It never explicitly names those siblings, but the input/output format makes the distinction obvious.

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 surfaces real constraints ('first-20-pages limit for scanned documents', 'automatic English OCR conditions'), which imply when the tool will and won't succeed. However it gives no explicit routing guidance against alternatives like mio_pdf_to_doc or mio_scanner_document, so the agent must infer selection from the tool name alone.

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