Convert Format

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

Annotations already provide idempotentHint=true, indicating repeated calls are safe. Description adds that it converts formats, but doesn't disclose whether input/output files are overwritten, if temporary files are created, or error handling. No contradiction with annotations (idempotentHint=true is consistent with conversion). Annotation contradiction: false.

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?

Description is concise (3 lines) with bullet-like listing of args. However, the Args section is essentially a duplication of the schema. Could be trimmed to just the first sentence plus a note about optional json_indent. Still, no wasted sentences.

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, description lacks info on return value (e.g., success message, error handling). However, conversion tools typically return success/failure. Parameter coverage is complete. Suggestions for additional context: output file overwrite behavior or format conversion limitations.

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%, so baseline is 3. The description adds value by listing all parameters and their types, which is redundant but helpful in a quick look. It also mentions a non-schema item (json_indent with default) and provides format enums inline. Slight extra value beyond schema.

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 that the tool converts between multiple specific formats (JSON, CSV, INI, YAML, TOML, XML, TOON). The verb 'converts' and the list of formats provide high specificity. Sibling tools like cc_fix_json or cc_validate_json are related but distinct, and the description differentiates by covering many 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 does not explicitly state when to use this tool versus alternatives. For example, if the goal is only to validate JSON, cc_validate_json might be better. However, the tool's broad format support implies it is the go-to for general conversion. No exclusion criteria or alternatives mentioned.

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