csv_sample

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

No annotations are present, so the description must fully disclose behavior. It only says 'get sample records' and 'various sampling strategies,' but does not explain default modes (first, count 10), how range works, whether headers are included, or any edge-case behavior. The schema covers some details, but the description adds little beyond its own purpose statement.

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, compact sentence with no redundant phrases. It is front-loaded with the action ('Get sample records') but could benefit from a brief mention of the modes or output without becoming verbose.

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?

With 5 parameters, 1 required, and no output schema, the description should explain what the tool returns and how the sampling modes behave. It only states the high-level purpose without covering important context like rangeStart/rangeEnd dependencies or default behavior, making it incomplete for effective use.

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%, so all parameters are described in the schema. The description's mention of 'various sampling strategies' hints at the mode parameter but adds no new meaning beyond the schema definitions. Baseline 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 clearly states the tool gets sample records from a CSV file using various sampling strategies, which distinguishes it from siblings like csv_inspect or csv_filter. It could be more specific by naming the strategies (first, last, random, range), but the core purpose is clear and distinct.

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. It does not mention that csv_tail might be used for last records, or that csv_search is for filtering. There is no exclusionary or comparative information.

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