compress-pdf

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'while maintaining quality' without addressing side effects such as whether the original file is overwritten, where the output is placed, or how compression level affects quality. This is a significant gap for a file-modifying tool.

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 a single, focused sentence that front-loads the core purpose and includes a meaningful qualifier. There is no redundant information, making it concise and well-structured.

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?

Without an output schema or annotations, the description should explain what happens on success, how output files are named and located, and default behavior when optional parameters are omitted. It fails to disclose whether the original file is replaced or a new file is created, leaving critical operational context missing.

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 documents all four parameters with full descriptions (100% coverage), so the baseline is 3. The description adds no additional parameter-specific meaning beyond what the schema provides, such as how compressionLevel relates to the 'quality' claim.

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 identifies the tool's function with a specific verb ('Reduce') and resource ('PDF document'), and the qualifier 'while maintaining quality' adds meaningful specificity. This distinguishes it from sibling PDF tools such as rotate or split.

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 for reducing PDF file size, but it provides no explicit guidance on when to use it over alternatives or when not to use it. While the purpose is clear, there is no mention of prerequisites, exclusions, or comparison to other tools, leaving usage only implied.

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