convert_file

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

Discloses key behaviors: saves result next to input, returns path, supports sync and async (wait parameter). No annotations exist, so description carries burden; minor gaps like error handling.

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?

Two concise sentences front-loaded with purpose, covering all key aspects without redundancy. Every sentence is informative.

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?

Covers core functionality, input/output, and async variant. No output schema, so path return is noted. Lacks detail on error states but adequate for typical use.

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 coverage is 100%, but description adds value: explains input types (local/URL, multiple for merge), to format vs tool slug, and options structure. Enhances 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 converts/processes files with GuruPDF, covering 100+ formats and PDF tools, and distinguishes from siblings like list_conversions (lists conversions) and get_status (checks job status).

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?

Provides clear context for when to use (convert files or run PDF tools) and implies when not to use (e.g., use get_status for job tracking). Could be more explicit about alternatives but is sufficient.

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