cache_dataset

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses that this is a purely local download with no execution/provenance records, explains the mutual exclusivity of dataset_rid/asset_rid, details behavior of materialize and exclude_tables, and outlines the return format. This is comprehensive for an operation with no side effects.

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: a clear one-sentence purpose, a brief use-case paragraph, an Args breakdown, and a Returns section. Every sentence adds necessary information for a tool with five parameters; there is no filler or 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 no annotations, an output schema (though not shown in the prompt), and five parameters covering two distinct modes (dataset vs asset cache), the description covers all necessary aspects: purpose, behavioral effects, parameter semantics, and return structure. It is complete and self-sufficient for an agent to select and invoke correctly.

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?

The description includes an 'Args:' section that explains all five parameters, including defaults, mutual exclusivity, version requirement, and when parameters are ignored. Since schema description coverage is 0%, this provides essential meaning beyond the bare schema and fully compensates for the lack of per-parameter descriptions.

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 opening line 'Download a dataset bag or asset into the local cache without creating an execution' clearly states the action and resource, distinguishing it from execution-creating tools. It also includes the specific use case 'warm the cache before running experiments', which further clarifies intent.

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 description gives explicit context ('Use this to warm the cache before running experiments') and mentions that no execution/provenance records are created, subtly indicating when not to use it. However, it does not explicitly name alternative tools or state direct exclusion criteria beyond 'not both' for parameters, so it stops short of a perfect 5.

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