json_to_csv

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

With no annotations, the description carries the full burden. It helpfully discloses the local-only, no-upload behavior, but says nothing about whether writing to outputPath overwrites existing files, what permissions are needed, or what happens when no outputPath is provided (returned string vs. file write).

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?

A single tight sentence with the core action front-loaded and the privacy constraint appended. No wasted words, though it packs multiple ideas into one clause chain.

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 4-parameter tool with no annotations and no output schema, the description covers the main conversion flow and the local-only guarantee, but omits the return behavior (CSV string vs. written file), overwrite semantics, and header handling, leaving meaningful gaps.

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 description coverage is 75%, so most parameters are documented in the schema. The description confirms outputPath is optional and the records/jsonPath are alternative input sources, but adds no syntax, format, or header-order detail beyond the 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?

States a specific verb+resource (convert JSON records/file to CSV) and clarifies input forms (inline records vs. a local JSON array file). It is clear and distinguishes the direction of conversion, though it doesn't explicitly contrast with the csv_to_json sibling.

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?

Provides a useful constraint ('Local files only — never uploads user data anywhere') and notes outputPath is optional, but gives no explicit when-to-use vs. when-not guidance or alternatives relative to siblings like csv_to_json.

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