load_dataset

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

With no annotations, the description carries full burden. It discloses return values (column names, row count, distinct values for categorical columns) and hints at in-memory loading. It does not fully detail side effects or error conditions, but for a load function, this is adequate.

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 well-structured: first paragraph for purpose and usage, second for return and metadata application, third for parameters. Every sentence is informative and earns its place, with no redundancy.

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 (loading datasets), the description covers the essential: input parameters, usage sequence, and output metadata. It integrates with sibling tools (find_drivers, explain_segment) and provides actionable guidance. Output schema exists, but description still explains return values, making it complete.

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 0%, so description compensates by explaining each parameter: name as a short label, path as absolute/relative path, separator with default and tab example, encoding with utf-8 default and cp1250 for Windows. This adds significant meaning beyond the schema.

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 verb 'load', resource 'CSV or ZIP-compressed CSV file', and the purpose 'into memory under a given name'. It also distinguishes itself from siblings by indicating it should be called ONCE before find_drivers or explain_segment.

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?

Explicitly states when to call ('ONCE before find_drivers or explain_segment') and that reloading the same file is unnecessary. Provides guidance on using returned metadata for find_drivers, including identifying target variables and exclusion lists.

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