optimize_pdf

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only describes what the transformation does. It doesn't state whether the operation is destructive (the overwrite param and output_path handling suggest in-place vs. copy behavior that is never explained), whether a password is needed for encrypted inputs, or what happens on failure.

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?

A single front-loaded sentence with no waste. It is appropriately terse, though the brevity contributes to the underspecification captured in other dimensions.

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 mutation tool with 6 parameters, no annotations, no output schema, and 0% schema coverage, the description is far too thin. An agent lacks the information needed to call it correctly (password handling, overwrite/output behavior).

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% across 6 parameters, and the description only touches on two of them indirectly (linearize, compress). It says nothing about password, overwrite, input_path, or output_path semantics, leaving the challenge of handling password-protected or in-place edits unexplained.

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?

States a specific verb+resource ('Shrink a PDF') and names the two operations (linearize, recompress), which distinguishes it from siblings like repair_pdf or flatten_pdf. However, it doesn't explicitly differentiate itself from those tools, so it falls short of 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 gives no guidance on when to use this tool versus alternatives such as repair_pdf, flatten_pdf, or encrypt_pdf. There are no prerequisites, no exclusions, and no routing cues for the agent.

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