convert_json_to_csv

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

The description lacks detail on behavior beyond the annotation 'readOnlyHint: false'. It does not clarify whether the tool returns a string, writes to a file, or handles edge cases like nested objects. The side effects implied by readOnlyHint false are not addressed.

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 overly terse, essentially restating the tool name. While concise, it lacks essential details that would justify its brevity, making it under-specified for an effective tool description.

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 tool's simplicity, the description omits critical context such as the expected JSON structure (array of objects), delimiter defaults, and output format. This leaves significant gaps for an agent trying to use it 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?

Schema coverage is 100% with adequate descriptions for both parameters (json and delimiter). The description itself adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 'Convert JSON to CSV format' clearly states the tool's purpose with a specific verb and resource. However, it does not distinguish from sibling conversion tools like convert_json_to_toml, leaving ambiguity about the exact CSV format produced.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, limitations (e.g., handling nested JSON), or cases where other tools might be more appropriate.

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