csv_to_json

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that output is returned inline in the tool result and that nothing is uploaded anywhere, which is meaningful for a file-processing tool. However it omits error behavior on malformed CSV, size limits, and how the delimiter affects parsing.

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?

Two short, front-loaded sentences with no wasted preamble. The trailing privacy assurance slightly duplicates the "local" qualifier already stated, but it is brief and arguably reassuring rather than filler.

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?

Absence of an output schema is mitigated because the description states results are returned in the tool result. For a simple two-parameter converter this is close to adequate, but the undocumented delimiter parameter leaves a real gap in a low-annotation definition.

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 only 50%: filePath is documented in the schema, but delimiter has no description anywhere — neither schema nor tool description explains accepted values, defaults, or delimiter detection. The description does not compensate for this gap.

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?

Names a specific verb (convert) and both source and target resources (CSV file → JSON records), so the transformation direction is unambiguous against siblings like json_to_csv. It does not explicitly reference the inverse tool, but the direction is clear enough to route correctly.

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?

"Local files only" is a scoping constraint rather than usage guidance. There is no explicit when-to-use, when-not, or named alternative (e.g. json_to_csv, validate_csv), so the agent must infer the selection context from the name alone.

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