download_competition_data

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

With no annotations, the description must disclose behavioral details on its own, but it only states the high-level download action. It does not clarify where files are saved, what the output_dir default behavior is, whether authentication or quota is needed, or what side effects occur. The verb 'download' conveys the core action but little else.

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 extremely short and front-loaded, with no filler, repetition, or unnecessary words. While brevity contributes to under-specification, the phrasing is efficient and immediately understandable at a high level.

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?

For a tool with no annotations, no output schema, and three undocumented parameters, the description is too minimal to enable correct invocation. It omits parameter roles, optionality, destination behavior, and the relationship to sibling download and listing tools, leaving significant gaps for an agent to guess.

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?

All three parameter descriptions are empty (0% schema coverage), and the description does not explicitly explain comp, file_name, or output_dir. It provides only minimal domain context through the phrase 'competition files,' which weakly implies that file_name refers to a file in a competition, but it does not compensate for the schema's missing parameter documentation.

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 uses a clear action-object pair, 'Download competition files,' which identifies both the operation and the resource type. It is distinct from dataset/model downloads and from listing operations like list_competition_files, though it does not explicitly distinguish itself from download_competition_replay or download_competition_episode_logs.

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?

No guidance is provided about when to choose this tool over alternatives such as list_competition_files, download_dataset, or download_competition_replay. There are no prerequisites, no exclusions, and no mention of whether file_name is optional or what happens when it is omitted.

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