Convert a JSON array of objects to CSV format, handling nested objects and custom delimiters such as semicolon, tab, or pipe.
Convert a JSON array of objects to CSV format. Handles nested objects and custom delimiters.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | JSON array of objects (e.g., '[{"name": "Alice", "age": 30}]') | |
| delimiter | No | CSV delimiter: "," (default), ";", "\t", or "|" |
Changes observed during successful MCP inspections.
v1.4.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint=true, so the agent knows this is a safe, non-mutating operation. The description adds 'Handles nested objects' but is vague about how they are flattened. No mention of output format or error behavior, but given annotations cover safety, a 3 is appropriate.
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?
One concise sentence with the primary action front-loaded. No redundant words, and every clause adds value (conversion, nesting capability, delimiter option).
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 conversion tool with 100% schema coverage and readOnly annotation, the description is adequate but lacks an explicit statement of the return format (e.g., CSV string) and how nested objects are serialized. These are minor gaps for an agent to call 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 covers both parameters fully (100% coverage). The description mentions 'custom delimiters' which aligns with the delimiter param, but doesn't add detail on nested-object handling relative to the data parameter. Baseline 3 is correct since schema does the heavy lifting.
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 ('Convert') and resource ('JSON array of objects to CSV format'), and adds distinguishing capabilities ('Handles nested objects and custom delimiters'). Clearly differentiated from sibling csv_to_json and other converters.
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 on when to use this tool versus alternatives. It doesn't mention when not to use it, or provide context for selection among the many conversion tools in the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.