xps_to_pdf

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the LibreOffice dependency, which is valuable context for execution. However, it does not describe potential side effects, error behavior, or output handling beyond the conversion itself, leaving some ambiguity.

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 with no fluff. It conveys the core purpose and a critical dependency efficiently, earning its place without 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?

For a simple conversion tool, the description is adequate but minimal. It does not explain default behavior for output_name, potential issues with the input path, or return values. Given the absence of an output schema and the incorrect schema parameter description, a bit more context would improve completeness.

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 parameters are already documented in the schema. The description adds no additional information about the parameters, such as format or constraints (e.g., that 'file' should be an XPS path, despite the schema erroneously saying 'PDF file'). Baseline of 3 is appropriate.

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 XPS document to PDF. The verb 'Convert' with explicit source and target formats makes the purpose unambiguous and distinguishes it from sibling conversion tools that handle other 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 when to use it (when you have an XPS document) and provides the prerequisite that LibreOffice is required. However, it does not explicitly mention alternatives or when not to use the tool. Since no other sibling tool handles XPS input, the guidance is adequate but not fully explicit.

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