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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context such as 'Runs in the browser' and details about credit coverage and pricing, which are not obvious from the tool name. However, it does not disclose the output format or return behavior, any potential destructive effects, or whether processing is synchronous. These are gaps for a transformation tool with no annotations.

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 description is front-loaded with the purpose and is reasonably sized, but it includes a significant amount of pricing and credit information that goes beyond what is needed for tool invocation. While this information may be relevant for access decisions, it is verbose and could be condensed. The core message is clear, but the extra details reduce conciseness.

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?

Given the tool has zero parameters and no output schema, the description covers the core purpose and access constraints. However, it does not explain how the PDF input is provided (e.g., through a file picker or session), nor what the output structure is (e.g., a download link or base64 content). These are notable omissions for a tool with no annotations or output schema, making it only minimally complete.

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 input schema has zero parameters, so the schema provides no semantic burden. Per the rubric, a baseline of 4 is appropriate for 0 parameters. The description adds a minor semantic detail ('by compressing images') but does not need to explain parameters since there are none.

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: 'Compress PDF — Reduce PDF file size by compressing images.' This is a specific verb (compress) and resource (PDF) with a clear mechanism (compressing images), and it distinguishes the tool from sibling PDF tools like mio_pdf_merge or mio_pdf_editor.

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 implies the tool is used when you need to reduce a PDF's file size, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The phrase 'Runs in the browser' gives some context, but there is no direct comparison to other compression tools or PDF operations.

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