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

With no annotations, the description must disclose behaviors. It fails to mention error handling for malformed JSON, handling of varying object keys, or CSV escaping rules. Extremely minimal.

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 sentence, 8 words, no fluff. Perfectly concise and front-loaded with the essential action.

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?

The tool has one input parameter, no output schema, and no annotation. The description should cover input format rules, edge cases (e.g., inconsistent keys), and output format details. It does none of this, leaving the agent underinformed.

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 0%, so the description should explain the 'text' parameter. It simply names 'JSON array of objects', not specifying that it must be a valid JSON string or expected encoding. Baseline would be 4 for 0 params, but one param exists and is underdescribed.

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 'Convert JSON array of objects to CSV text.' clearly states the verb (Convert), resource (JSON array of objects), and output format (CSV text), distinguishing it from sibling converters like csv_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?

The description provides basic intent but no guidance on when to use this tool vs other converters, nor any prerequisites or exclusions. It implies use for JSON array conversion but lacks explicit context.

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