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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the 500 MB size limit, browser-based execution, and output options (download individually or save together), plus error checking for missing entries. However, it omits critical details like whether the operation is destructive, what permissions are required, or what happens if the archive exceeds the 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?

The description front-loads the core action, but then includes an overly long and mostly irrelevant pricing/credits paragraph. The first sentence is also somewhat redundant (restating 'Extract Archive'). The marketing content does not earn its place in a tool description and bloats the overall length.

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 simplicity of the tool (zero parameters, no output schema, no annotations), the description covers the essential aspects: what it does, the size limit, output options, and error handling. It could be more complete by specifying supported archive formats or the behavior when the limit is exceeded, but it is largely sufficient for correct 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, so there is no parameter semantics to explain. The baseline for zero parameters is 4, and the description does not need to compensate for any schema gaps.

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: 'Extract files from one archive up to 500 MB.' It clearly distinguishes the tool from sibling tools like mio_pdf_zip by focusing on extraction rather than creation, but it does not explicitly name the sibling or state the inverse relationship, which would earn a 5.

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 usage by saying it extracts files from an archive, but it offers no explicit guidance on when to use this tool versus alternatives. There are no exclusions or conditions beyond the 500 MB limit, leaving the agent to infer the appropriate context.

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