Upload a replay

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description adds real context beyond them: attribution to the signed-in user, that the site parses the file, and that the response reports replay id plus whether an AI Coach report exists.

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?

Purpose and return values are front-loaded, but the final sentence with Windows and macOS default replay folder paths is operational trivia that does not affect tool invocation and bloats the definition for little selection value.

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 no output schema, the description helpfully states the return shape (replay id and AI Coach report existence) and implies authentication via 'signed-in user'. The only real gap is silence on what happens on duplicate uploads despite the idempotentHint annotation.

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 coverage is 100%, so both parameters are already documented with descriptions and the required/anyOf behavior. The description only restates that either a local path or download URL is accepted, adding no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Upload') plus resource ('StarCraft II replay / Brood War .rep') and destination ('StarCraft2.ai'). An agent can distinguish this from siblings like analyze_replay or list_my_replays without opening a schema.

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?

Implies usage via the two input modes (file path or URL) and notes it is free, but never states when to choose this over analyze_replay or how it relates to the downstream AI Coach flow. Context is implied rather than explicit, with no exclusions.

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