Tool Compress Pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively discloses that compression is lossy, uses image resampling via ghostscript, and that target_mb triggers a best-effort descent from ebook to screen quality. This is meaningful behavioral context beyond a simple 'compress PDF' statement, though it does not describe overwrite safety or output-file behavior.

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 exceptionally concise, with no filler. It front-loads the core purpose, then adds the key behavioral nuance about target_mb and quality descent. Every clause earns its place.

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 five parameters, zero schema descriptions, and no annotations, the description is not complete enough for an agent to confidently invoke the tool in all cases. The output schema may cover return shape, but the parameter semantics for output, overwrite, and path behavior are still missing, and the quality parameter's full range of allowed values is unstated.

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?

Schema description coverage is 0%, so the description must compensate for the five parameters. It adds meaning for target_mb (size target) and quality (values ebook and screen), but it does not explain path, output, or overwrite semantics. That leaves a significant portion of the parameter surface undocumented.

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 as compressing PDFs, specifies the underlying engine (ghostscript), and the lossy nature (image resampling). This is a specific verb+resource pairing that makes the tool's purpose unmistakable, and it is distinct from sibling tools which do other PDF operations.

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 to reduce PDF file size, and it explains the quality descent path (ebook→screen) when target_mb is set. However, it does not explicitly state when to use this tool versus alternatives, mention prerequisites, or call out situations where lossy compression would be inappropriate.

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