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

With no annotations, the description carries the full burden of behavioral disclosure. It states the core transformation but omits critical details such as whether the first row is treated as headers, handling of edge cases (quotes, newlines, empty values), and how the optional delimiter parameter behaves. This is a minimal description that leaves many behavioral aspects unspecified.

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?

The description is a single, clear sentence that is front-loaded with the essential verb and resource. It contains no filler or redundant information, making it highly concise and well-structured.

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 is relatively simple, and the description states the input and output formats ('CSV text' to 'JSON array of objects'). However, it lacks important contextual details such as whether the CSV is expected to have a header row and how the delimiter is applied. Given no output schema or annotations, the description should provide more context to be fully complete, but it does cover the primary purpose.

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?

The input schema documents both parameters (csv and delimiter) with descriptions, achieving 100% coverage. The tool description adds no extra meaning beyond what the schema already provides, but it does not need to since the schema is self-explanatory. Thus the baseline score of 3 is appropriate.

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 'Parse CSV text into a JSON array of objects' clearly specifies the verb (parse), resource (CSV text), and output (JSON array of objects). It distinguishes the tool from siblings like json_to_csv (reverse operation) and json_to_xml (conversion to XML), making its unique purpose immediately apparent.

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 is provided on when to use this tool versus alternatives. The description does not mention whether to use it for parsing CSV input or when not to, and there is no reference to sibling tools such as json_to_csv or filter. Users are left to infer the intended use from the name.

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