read_csv

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

The description discloses no behavioral traits. Given the absence of annotations, the agent is left uninformed about side effects, mutability, or operational characteristics.

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?

While single-sentence descriptions can be efficient, this one is critically under-specified. It prioritizes brevity over substance, achieving conciseness at the expense of useful information.

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?

Given the tool's complexity (5 parameters, including a nested options object) and the presence of many sibling tools, the description fails to provide any completeness. It does not explain the tool's relation to preview_csv or its role in the broader context.

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?

With 0% schema description coverage, the description should explain parameter meanings. However, it provides no clarification for any of the five parameters (path, limit, offset, columns, options), leaving the agent to infer from the schema alone.

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 only states it is a backward-compatible alias for preview_csv, without defining what preview_csv itself does. This leaves the purpose vague and forces the agent to seek additional information.

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 read_csv versus its sibling tools (e.g., preview_csv, inspect_csv). The description lacks any context for appropriate usage or alternatives.

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