json_to_csv

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

With no annotations provided, the description carries the full burden. It discloses a significant constraint (max 50,000 rows) and explains optional flattening behavior with dot-key examples. It does not detail error handling or output format, but the key behavioral traits are covered.

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 two sentences: the first states the core action, the second concisely covers key options and a limit. There is no redundant phrasing or filler. Every word earns its place.

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?

The tool has six parameters, no output schema, and no annotations. The description covers the main function, a limit, and three options, but misses output format (e.g., returns a CSV string), error handling, and the behavior of include_headers/newline. For a conversion tool with moderate complexity, this leaves some gaps that could affect correct invocation.

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 has 0% description coverage, so the description must compensate. It explicitly mentions delimiter, columns, and flatten, which maps to three of the six parameters. However, it omits newline and include_headers, and does not elaborate on how columns interact with the JSON keys. The dot-key example for flatten adds value, but the coverage is partial.

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 core function: 'Convert a JSON array of objects to CSV.' This is a specific verb+resource pair that distinguishes it from sibling tools like json_format or base64_encode. It also mentions configurable options, reinforcing the purpose.

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 context: when you have a JSON array and need CSV output. It provides clear context but does not explicitly state alternatives or when not to use the tool. Given the sibling set, this is sufficient for most cases.

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