read_csv

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the bare operation. It does not mention side effects like table creation/overwriting, error behavior, permissions, or schema inference. The agent cannot judge the tool's safety or effects.

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, concise sentence with no wasted words. It is front-loaded and easy to parse, though arguably too short. However, the brevity is appropriate for a simple tool, and the under-specification is penalized in other dimensions.

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 output schema exists, the return format need not be described, but the description still lacks essential context: filepath handling, table_name meaning, comparison with read_parquet, and error scenarios. With no annotations, this sparse description is not sufficient for an agent to invoke the tool reliably.

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 description says nothing about the parameters filepath and table_name. With 0% schema description coverage, the description does not compensate; it fails to clarify the filepath format, table_name semantics, or default behavior.

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 'Read a CSV file into a table' clearly states the verb (read), resource (CSV file), and outcome (into a table). It distinguishes from the sibling tool read_parquet by specifying the CSV format, making the purpose unambiguous.

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 vs alternatives like read_parquet or query. There are no usage contexts, prerequisites, or exclusions mentioned, leaving the agent without direction on choosing this tool.

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