get_file

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

With no annotations, description carries full burden. It discloses behavior: returns row preview for parseable CSV/TSV, provenance and artifact descriptor for binary, and mentions reading exact bytes at a cache URI. Lacks details on errors, idempotency, or side effects, but covers key behavioral aspects.

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 compact (4 sentences), front-loaded with main action, and uses bullet-style listing. It is clear and efficient, though a slight rephrase could reduce 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 presence of an output schema, the description need not detail return values, but it adequately covers return types for different cases. However, the lack of parameter explanations leaves the tool partially incomplete for invocation.

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%, but description does not explain parameters 'dataset_id' or 'refresh.' It only mentions selection from find_series, leaving parameter purpose unclear. This is a significant gap.

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 explicitly states 'Download a curated file artifact selected from find_series,' clearly indicating action and resource. It distinguishes from siblings by specifying it serves direct file types like workbooks and delimited text, and references find_series as the selection step.

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?

Description provides context on when to use (after find_series) and what file types are served, but does not explicitly state when not to use or mention alternatives. The guidance is adequate but lacks exclusions.

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