repair-pdf

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

No annotations are provided, so the description carries full disclosure burden. It indicates an 'attempt' at repair, suggesting potential failure, but it does not state whether the original file is overwritten, what output is produced, or how failures are reported. This is a significant gap for a file-modifying tool.

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 sentence that directly states the tool's purpose without filler. The word 'attempt' adds useful nuance about reliability. It is appropriately concise, though it lacks additional operational detail that would not hurt conciseness.

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?

With no annotations or output schema, the description is the only source of operational context. It fails to disclose whether the tool modifies files in place, what happens on failure, or what a successful repair produces. Given the 3-parameter schema is clear, the missing behavioral context leaves the tool incomplete for safe autonomous use.

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 input schema already provides descriptions for all three parameters (file, outputDir, outputFilename), giving 100% coverage. The description adds no additional parameter semantics beyond what the schema states, 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 a specific verb 'repair' and clearly identifies the resource 'damaged or corrupted PDF document', distinguishing it from sibling tools like rotate-pdf or merge-pdfs. The purpose is unambiguous and precisely scoped.

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?

Usage context is implied: you use this tool when a PDF is damaged or corrupted. However, there is no explicit guidance on when not to use it or any alternatives. The single-purpose nature makes the context reasonably clear, but exclusions are absent.

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