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

With no annotations, the description carries the full burden and does notable work: it discloses error behavior (duplicate headers, inconsistent columns), type behavior (values remain strings), privacy handling (inputs are not stored), and the absence of auth requirements. It doesn't mention rate limits or output shape in detail, but this is strong disclosure for an unannotated tool.

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?

A single dense sentence, front-loaded with purpose and cost/no-key status, followed by capability limits, error rules, and privacy notes. Every clause carries information an agent needs and nothing is padded.

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 conversion tool with no output schema and no annotations, the description covers the essentials: capabilities, size limits, error conditions, value typing, and data handling. The remaining gap is the unexplained input parameters, which is the only thing an agent would still have to infer.

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% and the description never addresses the three parameters. The boolean 'header' flag and the 'delimiter' enum (comma/semicolon/tab) are left entirely unexplained, and even 'CSV/TSV' only obliquely hints at delimiter control. The parsing traits mentioned (quoted fields, multiline cells) describe behavior, not parameter meaning.

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 resources (CSV/TSV to JSON), making the purpose unmistakable. It cannot be confused with any sibling such as html_to_markdown or json_inspect, and the 'no API key' qualifier further pins the tool's identity.

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 lays out clear applicability boundaries — 200 data rows, 50 columns, no API key — which tell an agent when the tool is and isn't a fit. It stops short of naming an alternative or explicitly stating exclusions, so it lands below the explicit when/when-not tier.

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