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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description adds little behavioral context beyond mentioning LibreOffice. It does not explain what happens to the input file, whether the conversion occurs asynchronously, or what side effects to expect, so the description carries minimal weight beyond annotations.

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 sentence that is front-loaded with the key purpose, includes the output format, and even names the underlying tool. There is no redundant or filler content.

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?

Given the tool's simplicity—one binary parameter and a direct format conversion—the description plus schema provides sufficient information for an agent to select and invoke it. The absence of an output schema is acceptable since the result (PDF) is explicit in the name and description.

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 documents the only parameter ('file') with full coverage and a description 'Input file (RTF).' The tool description adds no new semantic detail beyond restating that the input is an RTF document, so it meets the baseline but does not improve on 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 states a precise verb and resource: 'Convert an RTF document to PDF using LibreOffice.' This clearly distinguishes the tool from sibling converters like pdf_txt_to_pdf or pdf_html_to_pdf, which handle different input 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?

The description implies the tool should be used when the input is an RTF document, but it does not explicitly mention alternative tools or conditions when not to use it. The usage context is inferable from the title and input schema, but not explicitly stated.

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