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

Annotations include readOnlyHint=true and openWorldHint=false, which already communicate that this is a safe, read-only operation with a closed world. The description adds value by specifying the exact contents of the list (source format, output format, target id) without contradicting the annotations. It does not mention pagination or ordering, but these are not critical for a zero-parameter list tool.

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 concise sentence, front-loaded with the action ('List every conversion') and then provides essential detail about the returned fields. No redundant wording or repetition of the title or annotations. Easily parseable at a glance.

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 zero-parameter, non-destructive list tool, the description is complete: it names the resource, specifies the output content, and even links to the downstream process (convert_file). With annotations covering the read-only nature, an agent has everything needed to call the tool correctly and interpret the result. No output schema exists, but the description effectively substitutes for it.

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 tool has zero parameters, so the baseline is 4. The description correctly does not attempt to explain parameters that don't exist. The schema coverage is 100% (trivially, since there are no properties), so nothing further is needed.

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 uses a specific verb ('List') and resource ('conversions CutConvert supports') and clearly states what it returns: source format, output format, and target id. This distinguishes it from siblings like convert_file (which performs conversion) and inspect_file (which inspects). No ambiguity about what the tool does.

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 mentions the target id 'to pass to convert_file', which signals the primary use case: retrieve supported conversions before calling convert_file. It implies usage context but does not explicitly state alternatives or exclusions. For a simple listing tool, this is clear enough; a fully explicit 'use this to discover available formats before converting' would push it to 5.

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