document_to_pdf

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the conversion action and lists formats but does not disclose whether the operation is synchronous or asynchronous, how results are retrieved, any authentication requirements beyond the schema, or other side effects. The reference link is not a substitute for behavioral detail.

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 concise—two sentences—and front-loaded with the core action. The reference link is arguably useful for deeper documentation but adds slight noise. Overall, it is efficient without being under-specified.

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?

Despite having 7 parameters and no output schema or annotations, the description provides minimal context. It does not explain the return value, whether the conversion is asynchronous (suggested by siblings like wait_job_completion), or any prerequisites beyond the URL. This leaves significant gaps for an agent to know how to use the tool effectively.

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 already provides 100% coverage for all parameters, so the baseline is 3. The description adds meaningful value by expanding the supported file types in the 'url' parameter beyond what the schema lists (e.g., adding XLS, JPG, CSV, etc.), thereby enriching the understanding of the most important parameter.

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 converts various document types into PDF and explicitly lists the supported formats, which gives a specific verb and resource. However, it does not explicitly differentiate itself from sibling tools like csv_to_pdf or image_to_pdf, so it lacks direct sibling differentiation.

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 usage context is implied by the listed formats—if you have one of those formats, this tool can convert it. But there is no explicit guidance on when not to use it or mention of alternatives for specific formats (e.g., CSV to PDF, image to PDF), which would have made the guidance clearer.

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