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

With no annotations, the description carries the full burden. It adds context about running in the browser and billing/credit requirements, but does not disclose output behavior, input handling, or any limitations. The focus on pricing details does not compensate for the lack of operational transparency.

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 core purpose is front-loaded in the first sentence, but the description becomes verbose with billing and pricing information ('Covered by signup welcome credits...', 'See mioffice.ai/pricing...'). This extraneous detail reduces conciseness and shifts focus from operational guidance.

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 simple no-parameter tool, the description provides the essential purpose and some access context (browser, credits). However, it lacks details on expected input (e.g., how documents are provided), output format, and typical usage flow, which could leave the agent uncertain about invocation

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 has zero parameters and the input schema is an empty object. The description does not need to explain parameter details, and the baseline for 0 params is 4. No additional information is required.

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: 'Scan documents with auto edge detection, perspective correction & enhancement.' It uses a specific verb and resource, and the name 'Document Scanner' reinforces this. However, it does not explicitly distinguish this from sibling scanner tools like mio_scanner_id_card or mio_scanner_receipt.

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 provides no guidance on when to use this tool versus alternatives. It does not mention appropriate use cases, prerequisites, or exclusion scenarios. The billing information is present but does not help the agent decide when to select this tool.

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