email_to_pdf

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Convert email to PDF' and provides a reference link, without explaining whether it fetches remote URLs, how attachments are handled, authentication needs, or what the response looks like. This is a significant transparency gap for a tool with no annotation support.

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 very short and front-loaded with the core action. The reference link is arguably not useful for an AI agent, but it does not add significant clutter. Overall, it is appropriately concise, though it lacks the structured context that would make it more valuable.

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?

The tool has 7 parameters and no output schema, yet the description does not explain what the tool returns (e.g., a PDF link, job ID) or how it fits into workflows with siblings like wait_job_completion. It also does not mention the upload_file prerequisite for local files, which is only found in the url parameter description. With no annotations or output schema, the description is incomplete.

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 100%, so the baseline is 3. The description adds no parameter-level meaning beyond the schema; all useful semantics are in the schema itself (e.g., URL sources, margins, paperSize, embedAttachments). The reference link does not contribute 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 function with a specific verb and resource: 'Convert email to PDF.' This distinguishes it from sibling conversion tools like webpage_to_pdf, html_to_pdf, and document_to_pdf. No ambiguity about what the tool does.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Sibling tools like document_to_pdf or webpage_to_pdf exist, but the description does not mention how to choose between them. Schema parameter descriptions offer some context (e.g., URL sources, upload_file), but the description itself carries no usage direction.

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