convert_csv_to_json

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

No annotations provided; description only mentions 'CSV text with header row and data rows'. Does not disclose error handling, edge cases (e.g., quoted fields, missing values), or behavior for malformed input.

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 sentences plus a parameter line, front-loaded with purpose. No unnecessary words.

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?

Output schema exists (not shown) so return description is not needed. Lacks mention of delimiter assumptions, encoding, or size limits, but adequate for a simple 1-param tool.

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?

Input schema has only a 'csv' string with 0% coverage; description adds essential meaning: 'CSV text with header row and data rows', clarifying format and structure.

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 states 'Parse CSV text into structured JSON array' with a clear verb and resource. It distinguishes from siblings like convert_json_to_csv but doesn't explicitly differentiate from similar tools like tsv_to_json.

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 context ('from spreadsheets or exports into JSON format for programmatic use') but lacks explicit when-not-to-use or alternatives like TSV conversion.

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