pdf_convert

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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description does carry some burden. It discloses the failure shape ({success: False, error, error_type}) and that outputs are written to disk with an auto-generated name, which is useful. It does not state file-write permissions, overwrite behavior, or where output lands when output_dir/output_path are omitted.

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?

Front-loaded with a one-line purpose followed by return-format and example sections that are skimmable and well-labeled. Slightly padded because an output schema already exists, making the return-format section partially redundant, but the worked examples genuinely aid correct invocation.

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 6-operation tool, the description names every operation, shows two worked calls, and explains both success and failure payloads. Since an output schema exists, return values need not be restated; the remaining gap is the absence of operation-to-parameter mapping (e.g. from_images needing paths).

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 89%, so the schema already documents path, paths, html, markdown, dpi, fmt, output_dir, and output_path. The description adds no per-parameter syntax or format detail beyond that, so the baseline 3 applies even though the call examples show realistic argument combinations.

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 ('Convert between PDF and other formats'), enumerates the target formats, and the operation enum makes the directionality explicit. It does not, however, distinguish itself from siblings such as pdf_export, pdf_extract, or pdf_do, which an agent must choose among from a 16-tool family.

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?

There is no guidance on when to use pdf_convert versus pdf_export or pdf_extract, nor on prerequisites such as whether the PDF must already exist on disk. Usage is only implied through the operation enum, leaving the selection decision to inference.

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