email_to_pdf

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

With no annotations, the description carries the full transparency burden. It does disclose that the output includes headers and body, which is a behavioral detail. However, it does not mention side effects, file overwriting behavior, permission requirements, or attachment handling, leaving some ambiguity about what the conversion actually does.

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, concise sentence that front-loads the action and includes only essential information. Every word earns its place, with no fluff or repetition.

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 simple conversion tool, the description covers the core action. However, it lacks information about output behavior (e.g., return value, whether attachments are included, overwrite policy) and the schema contains a misleading parameter description. The description is adequate for basic use but not fully complete for edge cases.

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%, giving a baseline of 3. The description adds meaningful clarification by specifying the input is an .eml email file, which corrects the schema's misleading 'file' description that says 'PDF file'. This prevents an agent from passing the wrong file type. No additional detail about output_name is provided, but the schema already covers it.

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 uses a specific verb 'Convert' and clearly identifies the source ('email file (.eml)') and target ('PDF') with an explicit detail of including headers and body. This distinguishes it from sibling conversion tools, which handle different formats.

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 explicit guidance is given about when to use this tool versus alternatives or when not to use it. The description implies the use case (converting .eml files to PDF) and the tool's unique purpose among siblings, but it does not state exclusions or alternative options.

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