rtf_to_pdf

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

With no annotations, the description must disclose behavioral traits, but it only states the conversion itself. It does not mention output path handling, error cases, file format expectations, or any side effects. The schema's file parameter description is also misleading ('Absolute path to the PDF file') and the tool description does not clarify that the file is the RTF source.

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, focused sentence that is efficient and easy to parse. No unnecessary words 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 is minimally adequate but leaves gaps: it does not explain the output_name parameter beyond what the schema already says, and the incorrect file parameter description in the schema is not corrected. The overall context is clear enough for an agent to act, but missing details could lead to misuse.

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 covers 100% of parameters, so baseline is 3. The description adds limited meaning by implying that 'file' is the RTF input, but it does not explicitly map parameters or clarify the misleading schema description for 'file'. No additional parameter-level detail is provided beyond the schema.

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: converting an RTF document into a PDF. It uses a specific verb ('Convert') and resource ('RTF document') and distinguishes it from sibling converters like txt_to_pdf or markdown_to_pdf.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, input validation, or scenarios where RTF conversion is preferred over other formats.

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