util_json_to_csv

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

No annotations are provided, so the description must disclose behavioral traits. It only states the conversion direction without mentioning error handling, input validation, size limits, or what happens with malformed input. This lack of detail leaves the agent uncertain about tool behavior.

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 a single concise sentence that front-loads the purpose and use cases. It could be slightly more detailed without becoming verbose, but it is 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 conversion tool with no output schema, no annotations, and a single loosely-typed parameter, the description lacks essential details about input format, output structure, and edge cases. It is insufficient for an agent to confidently invoke 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 0% with one loosely defined parameter 'arguments' (object, additionalProperties). The description adds that input should be 'structured JSON rows', implying a collection of similar objects, but does not specify the required shape or nesting constraints. Given the open schema, more precision is needed.

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 structured JSON rows to CSV, with specified use cases (exports, spreadsheets, handoff). It distinguishes itself from the sibling 'util_csv_to_json' which does the reverse.

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 mentions use cases but does not explicitly say when to use this tool vs alternatives or when not to use it. The sibling 'util_csv_to_json' provides a contrast, but no direct guidance is given.

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