convert_to_pdf

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

No annotations provided, so description must cover behavioral aspects. It discloses installation requirement and return format, but omits side effects (e.g., whether document is closed or modified), fails to mention that the document must be open, and doesn't address overwrite behavior or error states.

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?

Extremely concise: two sentences plus a bullet. Each element earns its place: action, requirement, parameter, return. No fluff or 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?

Tool is simple, and description covers purpose, parameter, and return. However, lacks contextual details like prerequisite that document must be open, or behavior if output_path exists. Slightly incomplete for a mutation tool with no annotations.

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?

Only parameter output_path has no schema description. The description provides its purpose ('Destination path for the output PDF file'), adding meaningful context beyond the schema's type string.

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?

Tool name and description clearly state conversion of open document to PDF. The description specifies the method (LibreOffice headless) and distinguishes from other tools like export_markdown.

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?

Description mentions requirement (LibreOffice installed) but gives no explicit guidance on when to use vs alternatives, nor any when-not conditions. Usage is implied rather than explicit.

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