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 is covered by signup credits and Day Pass, but it does not explain what invocation returns, whether it launches an interactive UI, or any permission or processing behavior.

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 opening sentence is front-loaded and useful, but the trailing pricing and workspace-credit text is marketing copy that does not help an agent select or invoke the tool. It is not badly bloated, but several sentences do not earn their place.

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 output schema, the description explains what the tool is for and its output formats. However, it does not clarify the return behavior or what calling the tool actually does beyond running in the browser, leaving some ambiguity for an agent.

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?

There are zero parameters, so the baseline is 4. The description mentions Magic/Color modes and PDF/PNG/JPEG outputs, but these are UI workflow options rather than schema parameters; no additional parameter semantics are needed.

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 states a specific verb and resource: capture or import a whiteboard photo, then save as PDF, PNG, or JPEG. The term 'Whiteboard Scanner' and the erasure use case clearly distinguish it from sibling scanners for documents, receipts, barcodes, books, and ID cards.

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?

It gives a clear use context ('Keep a copy of the board before you erase it') but no explicit guidance on when to choose this over sibling scanner tools such as mio_scanner_document or mio_scanner_handwriting. The usage is implied rather than spelled out.

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