pdf_linearize

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that the file is restructured and that 'Content stays identical,' and it mentions the $0.01 cost. However, it does not clarify whether the original file is modified in place, how output_path behaves, or what the tool returns.

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 compact and front-loaded: the first sentence states the action and benefit, followed by use cases, a safety reassurance, and pricing. No filler or repetition is present.

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 three parameters, no output schema, and no annotations, the description leaves important invocation details unresolved, especially the behavior and meaning of output_path and idempotency_key. It is enough for high-level selection but not fully complete for correct invocation.

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 by explaining parameters. It only elaborates on the 'file' parameter by calling it a 'local path.' It does not explain 'output_path' or 'idempotency_key,' leaving two of the three parameters semantically underspecified.

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 states a specific verb and resource ('Optimise a PDF (local path)') and explains the actual transformation: 'the file is restructured so a browser can show page one before the whole document has loaded.' This clearly distinguishes linearization from sibling tools like pdf_compress or pdf_merge.

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?

It gives concrete target contexts: 'For document portals, archives and long reports.' This implies when the tool is appropriate, though it does not explicitly mention exclusions or name alternative tools such as pdf_compress for size reduction.

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