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

The only behavioral detail is 'browser-based tool,' which hints at client-side processing but does not disclose how the repair works, whether a downloadable file is returned, or what types of corruption are handled. With no annotations, the description carries the full burden and falls short.

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 short sentence with no filler. It is front-loaded with the core action and adds the 'browser-based' qualifier efficiently. Every word contributes meaning.

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, no output schema, and an empty input schema, the description is the only source of guidance. It explains the tool's purpose but omits how to invoke it, what input is expected, and what output the user receives. For a repair operation, this is insufficient context for an AI agent to use it confidently.

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 has zero parameters, so the baseline is 4. The description correctly does not invent parameters or add irrelevant detail. There is nothing more to explain about parameters.

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?

Description states a specific verb ('repair') and resource ('corrupted PDFs'), clearly distinguishing this from the many other PDF tools such as pdf-edit, pdf-join, and pdf-unlock. Though similar to the title, it adds the 'corrupted' qualifier and browser-based context, so purpose is unambiguous.

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?

No guidance is provided about when to use this tool versus alternatives. With sibling tools like pdf-unlock, pdf-edit, and organize-pdf, some indication of when repair is appropriate would be valuable. There is no mention of exclusions, prerequisites, or alternative tool recommendations.

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