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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the behavioral detail that results are grouped by number of steps and sorted with direct conversions first, which is useful. However, it does not disclose any edge cases, error behavior, or limitations beyond what the annotations imply. Since annotations carry the safety burden, a 3 is appropriate.

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?

A single, well-formed sentence that is front-loaded with the core action and then adds specific details about grouping and ordering. No wasted words; it is concise and efficient.

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 read-only listing tool with one parameter and an output schema (not shown but present), the description is complete. It explains the grouping and sorting of results, and the output schema covers return values. There is no missing information an agent needs to call this tool correctly.

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 schema already documents the 'from' parameter with a clear example ('png') and its meaning as an extension. The description does not add additional semantics about the parameter, relying on the schema. With 100% schema description coverage, the baseline is 3, and the description adds nothing extra for parameters.

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 a specific resource ('every format Convert To It can convert a given format to'), and adds detail about grouping by conversion steps and ordering. This clearly distinguishes it from siblings like check_conversion (which likely checks a specific conversion) and search_formats (which likely searches formats by name). The purpose is 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 usage: given a source format, list all possible targets. However, it does not explicitly discuss when to use this tool over the siblings or when not to use it. The guidance is implied rather than stated, so it meets the 'implied usage' level.

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