repair_pdf

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

With no annotations, the description carries the full behavioral burden but only discloses the mechanism ('reading and rewriting'). It says nothing about whether the original file is modified, how failures on irreparable PDFs are handled, or permission/error behavior — significant gaps for a mutation 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?

A single front-loaded sentence with no filler; the operation and mechanism come first. It is efficient, though arguably too terse for a four-parameter mutation tool.

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 four-parameter mutation tool with no annotations and no schema descriptions, the description omits parameter meaning, side effects, and success/failure behavior. It is not complete enough for an agent to call it correctly without guessing.

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% and the description explains none of the four parameters. It never mentions input_path, output_path, overwrite, or password, nor the interaction between output_path and overwrite, so it adds no parameter meaning at all.

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?

States a specific verb and resource: rebuild/repair a damaged PDF's structure, and adds the mechanism ('reading and rewriting'). An agent can tell this is a repair operation rather than extraction or optimization. It stops short of differentiating from near-siblings like check_pdf or optimize_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?

'Damaged PDF' implicitly signals the trigger condition, so usage is inferable. However, it gives no explicit when-to-use guidance, no note about first diagnosing with check_pdf, and no alternatives or exclusions.

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