repair_pdf

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

With no annotations, the description must carry the behavioral transparency burden. It discloses that the tool uses an external API and that output can be customized via directory/file name, but it does not disclose whether the original file is modified, whether authentication is required, or what the tool returns. This is a minimal level of disclosure.

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 two sentences, front-loads the purpose, and includes only essential information. No filler or redundancy.

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 is simple, but with no annotations and no output schema, the description should at least indicate the outcome (e.g., whether a repaired file is saved and where). It mentions output options but not the return behavior or side effects, leaving a gap in contextual completeness.

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?

The schema covers only file_path (33% coverage), but the description adds meaning to all three parameters: explicitly identifies the file path, and clarifies that output_dir and output_file_name are optional with clear roles. This compensates for the low schema coverage.

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 states the tool's function: 'Repair a damaged or problematic PDF' using a specific API. This is a specific verb+resource pairing that distinguishes it from sibling tools like compress_pdf or linearize_pdf.

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 provides clear context by specifying when to use it (for damaged or problematic PDFs) and how to invoke it (provide local file path, optionally specify output). However, it does not explicitly mention alternatives or exclusionary cases, so it stops short of full when-not guidance.

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