convert_to_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the action and return value ('Returns: Conversion confirmation with path'), but it does not mention side effects, whether existing files are overwritten, whether the document is modified, or whether permission or file-system constraints apply.

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 concise and well-structured, with a front-loaded purpose statement followed by clearly labeled Args and Returns sections. Every line earns its place and 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?

For a simple two-parameter conversion tool, the description is nearly complete: it explains both arguments, references open_document for the source ID, and states the return value. Minor omissions include whether the output path must end in .pdf and whether an existing file at that path is overwritten, but these do not seriously impair call correctness.

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 property descriptions are absent, so the description must compensate. It does so fully by explaining both parameters: doc_id is 'Document ID from open_document' and output_path is 'Output file path for the PDF.' This adds meaningful context well beyond the bare 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 specific verb and resource: 'Export document as PDF.' This is unambiguous and clearly describes the tool's operation. However, it does not explicitly differentiate this tool from sibling alternatives like export_page_as_image or save_as_image, so it falls short of a 5.

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 gives implied usage guidance by noting 'doc_id: Document ID from open_document,' which tells the agent that a previously opened document is required. However, it does not explicitly state when to use this tool versus alternatives such as export_page_as_image or batch_convert_files, nor does it provide any exclusion criteria.

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