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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds value by specifying what data is returned (source format, output format, target id) and confirming completeness ('every conversion'), which goes beyond the annotations. However, it does not describe any pagination, ordering, or error behavior, and for a simple list tool this is a minor gap given the annotation coverage.

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 that front-loads the core purpose ('List every conversion CutConvert supports') and then specifies the exact content (source, output, target id) and its downstream use. Every word earns its place with no redundancy or fluff.

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 that there are no parameters, no output schema, and annotations cover the read-only and non-destructive nature, the description fully equips an agent. It explains what will be listed and how the result relates to convert_file, leaving nothing critical missing for a simple listing tool.

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 there is nothing for the description to explain. Schema coverage is complete (100%) by default. The baseline for 0 params is 4, and the description does not introduce any parameter-related ambiguity or missing information, so it fully meets 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 states a specific verb 'List' and a precise resource: 'every conversion CutConvert supports', detailing exactly what is included (source format, output format, and target id). It clearly distinguishes from siblings like convert_file (which performs conversions) and inspect_file (which inspects files), making the tool's purpose unambiguous.

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 a clear usage context by noting the target id is 'to pass to convert_file', suggesting this tool is a discovery step before conversion. It doesn't explicitly state when not to use it or mention alternatives, but the relationship to convert_file is evident without requiring further inference.

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