csv_parse

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and repeatability profile is covered without the description. The description adds only that output is 'structured JSON rows', while leaving open important behavior such as header-row handling, quoting/escaping rules, and what happens with 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?

A single front-loaded sentence with no filler, and the input-to-output relationship is stated up front. It is efficient, though it trades away detail an agent might want for a parser with format-sensitive behavior.

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?

There is no output schema, so the description is the only place the row structure could be explained, and 'structured JSON rows' is vague about whether rows are arrays or objects keyed by header. For a two-parameter pure function with full annotation and schema coverage this is adequate but leaves a real gap around output shape and error handling.

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 100%, and both parameters (csv, delimiter with a stated comma default) are fully documented in the schema, so the baseline of 3 applies. The description contributes nothing beyond the schema about the delimiter or accepted CSV dialect.

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 verb+resource pair (parse CSV text) is specific, and the output target (structured JSON rows) is named, so an agent knows exactly what goes in and roughly what comes out. It does not reference any sibling tool or distinguish itself from the many other text/format converters in the catalog, which keeps it below a 5.

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?

There is no statement of when to use this tool, no prerequisites, and no comparison to adjacent tools such as markdowntable_convert or json_format. The intended usage is only inferable from the tool name and the single-purpose description.

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