repair_pdf

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the mechanism (reloading and re-saving) but does not state whether the original file is overwritten, whether a new file is created, or what happens to metadata or other properties. This lacks essential transparency 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?

The description is a single, focused sentence that immediately conveys the tool's purpose and method. Every word is meaningful, with no redundancy or extraneous content, making it highly concise and well-structured.

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?

Although the schema covers parameter descriptions, the description omits important behavioral context such as output file handling, potential failure modes, and prerequisites. With no annotations or output schema, the description is not complete enough for the agent to fully anticipate the tool's behavior and side effects.

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 fully documents both parameters with descriptions, so the baseline is 3. The description adds no additional parameter information beyond what the schema already provides, so it neither helps nor hinders parameter understanding.

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 purpose: repairing corrupted PDFs by reloading and re-saving with pdf-lib. The verb 'repair' and resource 'corrupted PDF' are specific, and no sibling tool shares this exact function, distinguishing it from the many conversion and manipulation tools.

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 implies use for corrupted PDFs but does not explicitly state when to use it over alternatives or provide exclusions. There is no mention of alternative tools or specific conditions, so the usage guidance is only implied, not explicit.

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