list_conversions

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

No annotations are provided, so the description carries the full burden. It only states the basic operation (listing) but does not disclose that it is a safe, read-only operation, nor any potential side effects, authentication needs, or rate limits. The agent must infer it is non-destructive from context.

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, clear sentence that is front-loaded with the core purpose. No extraneous words or information.

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 one optional parameter, no output schema, and sibling tools, the description is adequate but could be more complete. It does not specify the format of the returned list (e.g., array of objects with conversion details), which might help the agent anticipate output. However, for a simple listing tool, it suffices.

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% with a well-described parameter. The description adds that the filter is optional, which is already implied by the parameter being not required. The schema's description of 'from_format' with examples already provides the meaning, so the description adds only marginal value, aligning with the baseline.

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 verb 'list' and the resource 'conversions and tools GuruPDF supports', with an optional filter by input format. It distinguishes itself from sibling tools like convert_file, check_credits, and get_status by focusing on listing available capabilities.

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 usage for discovering supported conversions and tools, optionally filtering by input format. However, it does not explicitly state when to use this tool over siblings, nor when to avoid it (e.g., for actual conversion, use convert_file).

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