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 usefully disclose that the workspace consumes more credits per run than Document/Image/Scanner, that welcome credits cover only limited runs, and that Day Pass is excluded — real operational constraints. But it never addresses output quality, what compression settings are applied (notably there is no quality parameter at all), size limits, or whether the original 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?

Two sentences with zero waste, and the tool's own behavior is stated before any supporting detail.

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?

The description is dominated by marketing and billing copy — three separate sentences restate the credit-pack model, including a redundant "no per-workspace subscription" clause — while a dedicated sibling, mioffice_pricing_info, already exists for that. The compressed output itself is left undefined: no mention of quality trade-offs, output format, or how the result is delivered, which matters most for a zero-parameter tool with no output schema.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The absence of any quality or target-size parameter is unexplained but is a schema design gap rather than a description gap.

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?

States a specific verb and resource ("Compress Video") plus a short workflow ("Upload your video, process it, and compare the download with the original"). It does not distinguish itself from nearby siblings such as mio_video_resize, mio_video_enhancer, or mio_video_converter, so the agent must infer the boundary from the name alone.

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 when-to-use or when-not-to-use guidance and no named alternative; the only conditional content is billing (Day Pass exclusion, limited welcome-credit runs). Cost gating is not the same as selection guidance, and the one hint that matters — compare the download with the original — is framed as a workflow step, not a decision rule.

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