load_dataset

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

Annotations already cover read-only, open-world, and idempotent behavior. The description adds value by specifying the output summary (shape, column kinds, missing-data summary, top findings) and a behavioral constraint about not profiling immediately.

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 one compact, front-loaded sentence with no filler. The file types, return summary, and sequencing warning are all meaningful and concise.

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?

The description plus annotations cover safety and basic behavior, and the output schema can document return values. However, the optional parameters remain undefined, and the lack of differentiation from manage_sources leaves some invocation context incomplete.

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 description coverage is 0%, so the description must carry parameter meaning. It clarifies that source accepts common file formats, but it leaves alias, limit, and options entirely undescribed. This is insufficient for a 4-parameter tool.

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 names a specific verb ('Load') and resource (CSV, Excel, Parquet or JSON file) and states the immediate outcome. It is clear about what the tool does, but it does not explicitly distinguish itself from the sibling manage_sources.

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?

The intended use is implied: when you need to bring a file into the session. It includes a sequencing rule ('do not call profile straight after this'), but it does not state when to choose load_dataset over manage_sources or provide exclusions.

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