Sign in to StarCraft2.ai

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

Goes well beyond the annotations by disclosing the interactive flow: a browser page opens, the user approves externally, then the tool completes. It also surfaces a failure mode and recovery step (browser didn't open → show the result URL), which annotations cannot convey.

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?

Three tightly written sentences, front-loaded with purpose and precondition, with no redundant restatement of the name or title.

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?

No output schema exists, and the description compensates by telling the agent what the result contains (a URL) and what to do with it. Combined with the precondition, an agent has everything needed to invoke and handle this tool correctly.

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% and the single wait_seconds parameter is fully documented in the schema, so the baseline of 3 applies. The description does not elaborate on the wait behavior beyond implying the tool blocks until the user finishes, adding little over the schema.

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 (sign in) and resource (the user's StarCraft2.ai account), and explains the mechanism (browser OAuth with PKCE) so it is clearly distinguishable from siblings like logout and get_account.

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?

"Required before any other tool" gives explicit precondition guidance, and the fallback instruction ("if the browser didn't open, show the user the URL from the result") tells the agent what to do on failure. It stops short of naming alternatives or when-not conditions, so it is clear but not exhaustive.

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