csv_json

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

With no annotations, the description is the sole behavioral signal. It discloses that CSV→JSON produces an array of objects and JSON→CSV expects an array of objects, which is useful. However, it does not address delimiter behavior, malformed input, or any edge cases. For a stateless conversion tool this is adequate but not rich.

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 functional description is concise, using two sentences to explain the two conversion directions. However, the "[PRO — 3 trial uses left]" prefix is irrelevant to tool operation and adds noise, though it does not significantly harm readability.

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 simple tool with three parameters and no output schema, the description covers the conversion directions and return expectations (e.g., array of objects for CSV→JSON). It lacks usage guidance versus siblings, but given low complexity, the description is sufficiently complete.

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 already documents all parameters (100% coverage), but the description adds meaningful semantics: it specifies that JSON input must be an array of objects ("JSON→CSV converts an array of objects to CSV"), which is not explicitly stated in the schema's input description. This goes beyond the schema and helps the agent construct valid input.

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's function with a specific verb and resource: "Convert between CSV and JSON." It further details both directions (CSV→JSON and JSON→CSV), which distinguishes it from sibling tools like yaml_json. The phrasing is unambiguous and action-oriented.

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 by explaining what the tool does, but does not explicitly state when to use this tool versus alternatives like yaml_json or json_format. There are no exclusions or comparisons to siblings, so the agent must infer usage from the purpose alone.

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