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

With no annotations, the description carries full responsibility for behavioral disclosure. It reveals the internal process (iterating quality/resolution, re-encoding as JPEG), rate limits (20 calls/day per IP), file size limits (10MB), and even mentions the need for an API key for larger files. This is thorough and goes beyond a simple 'compress' statement.

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 somewhat long but front-loaded with the core purpose and method. Each sentence adds useful information (usage, limitations, alternatives), though some might find the API key and website details excessive. It remains efficient and focused.

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 tool with no annotations and no output schema, the description is remarkably complete. It covers purpose, method, usage context, file size and rate limits, alternatives for larger files, and even where to obtain API keys. It does not explicitly describe the return value, but for a compression tool this is implied and acceptable.

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 schema already provides 100% coverage of parameter descriptions, so the baseline is 3. The description adds value by explaining how quality and target_size interact (iterating quality/resolution) and gives concrete examples (e.g., 500KB, 1MB), enriching the semantic understanding beyond the schema.

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 compresses PDFs to reduce size, and explains the method (rendering pages and re-encoding as JPEG). However, it does not distinguish itself from the sibling tool 'optimize_pdf', so it lacks explicit sibling differentiation.

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 explicitly says 'Use this when a user wants to shrink a PDF' and provides examples (500KB, 1MB, 'smaller'). It also gives clear alternatives for larger files (API key or the free website), effectively covering when to use and when not to use this tool.

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