download_replay

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

With no annotations provided, the description carries the full burden. It discloses the caching side effect, the multi-stage download progress with percentages, and the return type. It does not mention potential failure modes or cleanup options (e.g., delete_replay), but covers the primary behavior transparently.

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-organized with clear sections for purpose, usage advice, progress stages, arguments, and return value. Each sentence adds necessary detail, and the critical first sentence immediately states the tool's function.

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 this is a download/caching tool with a single parameter and an output schema, the description covers all necessary context: when to use it, expected download time, caching semantics, progress reporting, and the returned response type. It integrates well with the sibling analysis tools by prescribing its use first.

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 schema only defines match_id as an integer with no description. The description compensates fully by explaining it is 'The Dota 2 match ID (from OpenDota, Dotabuff, or in-game),' adding source context and practical meaning.

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 opens with 'Download and cache the replay file for a Dota 2 match,' which clearly identifies the action and resource. It also distinguishes itself from the many analysis sibling tools by instructing to 'Use this tool FIRST before asking analysis questions about a match.'

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?

Explicitly states when to use the tool: 'Use this tool FIRST before asking analysis questions about a match.' It also provides important usage context about file size, download time, and caching behavior that informs whether to invoke it.

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