load_dataset

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

No annotations provided, so description bears full burden. It mentions return value but omits behavioral traits like file access permissions, error handling, or side effects. Minimal behavioral disclosure.

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?

Description is concise with a brief introductory sentence and a clear args section. It is front-loaded and efficient, though the docstring format is slightly redundant with the structured schema.

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 simple tool with 1 param and output schema existing, description covers basic usage and return. Missing details on error cases, file access, and prerequisites, but adequate for straightforward load operation.

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?

Only one parameter 'path' with schema coverage 0%. Description adds meaning: 'Absolute path to a .h5td/.h5ad file', specifying path type and file format, which is useful beyond the bare 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?

Description clearly states 'Load a TreeData file' with specific file extensions (.h5td, .h5ad) and mentions returning a dataset_id handle and summary. It distinguishes from sibling load_example_dataset by specifying 'existing datasets'.

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?

Explicit instruction 'Use this for existing datasets that already contain trees, expression, and/or a character matrix' guides when to use. No explicit when-not-to-use, but context implies load_example_dataset is for examples.

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