download_competition_episode_logs

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only names the action and target resource; it does not describe what files are written, how output_dir is used, what agent_index means, or how failures are handled.

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 a single concise sentence with the verb and object front-loaded. There is no filler, though the extreme brevity sacrifices behavioral and parameter detail.

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?

With three parameters, no annotations, no output schema, and 0% schema description coverage, a one-line description is insufficient. An agent cannot tell whether agent_index selects one agent or filters within the download, where files are written, or what the tool returns.

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 compensate. It lightly hints at episode_id ('simulation episode') and agent_index ('agent logs'), but output_dir is completely unexplained and the agent_index behavior is ambiguous. This does not meaningfully compensate for the empty schema 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 description states a clear verb ('Download') and a specific resource ('agent logs for a simulation episode'), which distinguishes it from sibling tools like download_competition_replay or download_competition_data. It does not explicitly name a competing sibling, so it stops short of a 5.

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 use this tool instead of related tools such as download_competition_replay, kernel_logs, or list_competition_episodes. There are no exclusions, prerequisites, or alternative-selection conditions.

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