csv_inspect

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

With no annotations, the description carries the full burden. It discloses that the tool returns an overview including preview data, implying read-only behavior, but it does not mention performance implications, error handling, or whether it reads the entire file. Enough to understand basic behavior, but not deeply transparent.

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, focused sentence that immediately states the action and key outputs. It is concise and front-loaded with the verb, with no unnecessary detail.

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 moderate tool with 2 parameters and no output schema, the description provides a reasonable overview but lacks details on output format or edge cases. It is adequate for basic understanding but incomplete for advanced usage scenarios, especially given the suite of similar CSV tools.

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 coverage is 100%, with file and previewRows already documented in the schema. The description adds no additional parameter semantics; it just lists output features. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the tool provides an overview of a CSV file with specific outputs like size, row/column count, delimiter, and preview. The verb 'get an overview' is specific, but it does not explicitly distinguish itself from sibling tools like csv_stats or csv_sample, which can also provide some of these details.

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 given on when to use this tool versus alternatives like csv_sample or csv_stats. The description implies a general overview use case, but with many sibling tools, the lack of explicit exclusion or alternative hints leaves the agent without clear selection criteria.

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