accounts_refresh

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

With no annotations provided, the description must disclose side effects and expectations itself. 'Re-discover' implies an active refresh, but the description does not state whether the operation is safe, requires authentication, mutates account state, or what the tool returns.

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 two sentences long, states the purpose first, and contains no filler or redundant content. Every part of the text earns its place.

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 tool with no output schema and no annotations, the description should clarify expected output and prerequisites such as an authenticated session. It states the tool's purpose and parameter logic adequately for a minimal one-argument tool, but leaves room for an agent to guess at the refresh behavior and return contract.

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 has no property description, but the tool description compensates by explaining the meaning of account_id and the rule for omitting it when only one account is logged in. This is sufficient for a single optional parameter, though no format or example is included.

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, 'Re-discover,' and names the specific resource ('game roles (uids) for an account'). This clearly differentiates the tool from the sibling accounts_list tool, which would list accounts rather than refresh role discovery.

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?

The description gives explicit invocation guidance for the parameter: pass account_id, or omit it when only one account is logged in. However, it does not mention when to prefer this tool over alternate workflows such as the login/auth tools or accounts_list, so the broader usage context is left implied.

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