Convert a file (by URL) to PDF

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

The description discloses credit cost, return format (embedded resource), and auto-detection behavior. Annotations include 'openWorldHint: true', which is consistent with credit deduction. No contradictions, but error cases or timeouts are not mentioned.

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?

Two sentences, front-loaded with the core purpose. Every sentence adds necessary information without redundancy.

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 9 parameters and no output schema, the description explains the main workflow, supported formats, cost, and return type. It omits high-level guidance for optional parameters like page ranges or passwords, but the parameter descriptions cover those.

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 coverage is 100%, so baseline is 3. The description adds value by explaining auto-detection and listing supported file types, enriching understanding beyond individual parameter descriptions.

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 'Convert a file fetched from a public URL into a PDF' with a specific verb and resource. It lists supported file types but does not explicitly differentiate from sibling tools convert_html and convert_markdown, which are more specific.

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 covers when to use the tool (converting a file from a public URL to PDF) but lacks guidance on when not to use it or how it compares to siblings. No alternatives or exclusions are mentioned.

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