pdf_compare_files

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

No annotations are supplied, so the description carries the full behavioral burden. It reveals what is detected (text differences, page count mismatches) but not whether the operation is read-only, whether it works on scanned or image-only PDFs, how large files are handled, or how failures on one file are reported.

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 well-formed sentence with the action and scope front-loaded and no filler wording. It is exactly as long as it needs to be.

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?

There is no output schema and no annotations, so the description needed to explain the shape of the result - what a difference report looks like, whether it is per page or aggregated - and it does not. For a two-file comparison tool with no structured return-value documentation, this leaves a material gap.

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 100%, with both parameters ('Path to the first/second PDF file') documented in the schema itself. The description adds only the framing that the two inputs are compared to each other, which is marginal but consistent with the schema-driven baseline of 3.

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 names a specific verb (compare) and resource (two PDF files) and states the scope of comparison: page-by-page text differences and page count mismatches. That is far more informative than the bare tool name, though it never names a sibling tool to contrast with, which is why it stops 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?

There is no guidance on when to use this versus alternatives such as pdf_read_text or pdf_get_metadata, and no mention of preconditions (both files must exist and be readable PDFs). The agent must infer usage entirely from the tool name and description.

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