linearize_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 explains the purpose but does not state whether the original file is modified in place, what happens if output_name is omitted, whether the operation is reversible, or any potential side effects. The term 'linearized' is technical and not explained.

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 immediately states the core purpose. It is concise, front-loaded, and contains no fluff, making it easy to scan.

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 simple two-parameter tool with no output schema, the description provides the essential purpose but lacks important context about default output behavior and side effects. Users would need to rely on the schema or trial/error to understand whether the original file is overwritten or a new file is created. This makes it minimally adequate but incomplete.

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?

Input schema covers 100% of parameters with descriptions (absolute path for file, output path with default for output_name). The tool description adds no extra meaning beyond what the schema already provides, so baseline 3 is appropriate.

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: 'Optimize a PDF for fast web viewing'. It uses a specific verb (optimize) with a resource (PDF) and provides a concrete goal (fast web viewing), which distinguishes it from sibling tools like compression or format conversion.

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?

There is no guidance on when to use this tool versus alternatives such as compress or pdf_to_pdfa. The description implies web-focused optimization but does not state when it is appropriate, when not to use it, or which tools might be better suited for other scenarios.

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