download_competition_replay

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 implies a read-only fetch via the verb 'download' but does not disclose output format, file type, file size, authentication requirements, or what a 'replay' actually contains (visual sim data, event frames, etc.).

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 (four words), but this is under-specification rather than disciplined conciseness. It essentially restates the tool name with no added content, so brevity is not earning its place alongside useful information.

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 download operation with two parameters, no annotations, no output schema, and many similar download siblings, this description is grossly inadequate. An agent cannot determine what is returned, whether `output_dir` is required in practice, what file artifacts to expect, or how this differs from `download_competition_episode_logs`.

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%, and the description adds zero parameter meaning beyond what the names suggest. The parameter names (`episode_id`, `output_dir`) are intuitive enough to hint at their roles, but the description neither confirms the expected format of `episode_id` nor explains the behavior or default of `output_dir`, so it fails to 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 uses a specific verb ('Download') and a specific resource ('simulation episode replay'), which clearly identifies the action. However, it does not differentiate from the closely related sibling `download_competition_episode_logs`, and the meaning of 'replay' versus 'logs' is left to the agent to infer.

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 given on when to use this tool versus alternatives. The sibling list includes `download_competition_data`, `download_competition_episode_logs`, `download_dataset`, and `download_model_version`, but the description provides no selection criteria or exclusions to help an agent route correctly.

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