compare_pdfs

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

With no annotations, the description carries full responsibility for behavioral disclosure. It states the tool compares and reports on page count, text, and size, but does not specify the output format, potential side effects (e.g., file modification), or limitations with encrypted or scanned PDFs. This is adequate for a simple read-only tool but lacks depth.

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, front-loaded sentence with no filler. It efficiently conveys the tool's action, objects, and outcome.

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?

The tool has a simple two-parameter interface with 100% schema coverage, and the description covers the core functionality and the three comparison aspects. Without an output schema, the description could be more explicit about the report's structure, but for a straightforward compare tool it is reasonably complete.

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?

Both parameters are fully described in the schema with 'Path to first PDF' and 'Path to second PDF'. The description does not add any extra semantic value beyond the schema, so the baseline of 3 applies.

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 uses the specific verb 'Compare' with 'two PDFs' and lists the exact dimensions of comparison (page count, text, size). This clearly differentiates it from sibling tools like pdf_to_markdown or pdf_reader, which focus on conversion or reading rather than comparison.

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 makes the use case clear: comparing two PDFs. However, it does not explicitly state when to use this tool over any alternative, nor does it mention any complementary tools or exclusions. Since no other sibling tool offers comparison, the context is self-evident, but explicit guidance is missing.

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