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

The description discloses the return structure as a dict with status, output_path, output_format, preview, and optional error. It also lists all supported conversions. However, it does not mention whether the original file is modified, if output overwrites anything, or any permissions required. Since there are no annotations, the description carries the full burden, but it does provide core behavioral information.

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 compact and well-structured with a heading, a list of supported conversions, and a return type. It is front-loaded with the purpose, and every line earns its place, though it could elaborate on parameter meanings without bloating.

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 the low schema coverage and lack of annotations, the description provides the essential information: supported conversions and return format. However, it leaves ambiguity about parameter semantics and doesn't mention file system interactions or error conditions beyond the optional error key. It is mostly complete but has room for improvement.

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 has no descriptions, so the description must compensate. The conversion matrix implies that 'path' is the source file and 'fmt' is the target format, but this is not explicitly stated. The allowed values for fmt are not enumerated directly, but can be inferred from the matrix. This is partial compensation, but not fully explicit.

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 tool converts file formats and lists all supported conversion paths in a table. This is specific and distinguishes it from the unrelated sibling tools, so an agent knows exactly what this 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 does not explicitly state when to use this tool versus an alternative, but given the sibling tools are unrelated, there's no confusion. The conversion matrix implicitly communicates the use case: if you need any of these conversions, use this tool. It doesn't mention when not to use, but that's acceptable given the scope.

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