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

The description discloses key behavioral details: returns a temporary download URL (valid 1 hour) and that the file is deleted within 24 hours. These details are beyond what annotations provide (readOnlyHint=false, destructiveHint=false) and give the agent important lifecycle information. No contradiction with annotations exists.

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 at 3 sentences, each serving a distinct purpose: stating the core action, specifying parameter rules, and detailing the return behavior. No extraneous information is included, making it easy for an agent to parse quickly.

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 no output schema, the description adequately explains the return format (temporary URL with expiry) and data retention. It covers all input modalities and constraints. The presence of sibling tool name provides context. The description is complete for a conversion tool of moderate complexity.

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?

The input schema already describes all 5 parameters (100% coverage), setting baseline at 3. The description adds semantic value by explaining the mutual exclusivity of source_url and base64_content, specifying the ~5MB limit for base64, and noting that source_format can be auto-detected. This enhances the agent's understanding beyond the schema's per-parameter descriptions.

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 begins with a clear verb-resource pair: 'Convert a file from one format to another.' This immediately identifies the tool's core function. It also distinguishes itself from the sibling tool 'list_conversions' by focusing on performing the conversion rather than listing available 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 explicitly states the two mutually exclusive input methods (url vs base64) and clarifies that exactly one is required. It provides guidance on when to prefer each (URL for large files, base64 for small files) and mentions auto-detection of source format. However, it does not explicitly state when not to use this tool or compare it to alternatives beyond the sibling.

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

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

Annotations already declare readOnlyHint=true, so the description need not restate safety. The description adds the filtering behavior, which is useful but not extensive behavioral 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?

Two sentences efficiently communicate the purpose and optional filter, with zero unnecessary words. Front-loaded with the main action.

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 tool with one optional parameter and no output schema, the description fully covers what the agent needs to know: what it lists and how to filter.

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 the parameter already described, but the description adds meaning by explaining the filter effect and providing an example ('docx' returns all DOCX target options), enhancing understandability.

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 resource 'supported conversion routes', and implicitly distinguishes from sibling 'convert_file' by indicating this tool provides options for conversion rather than performing the conversion.

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?

It specifies when to use the tool (to list conversion routes, optionally filtered by source format) and gives a concrete example. However, it does not explicitly state when not to use it or mention alternatives beyond the sibling.

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