Switch Active Account

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

Annotations provide only non-destructive and open-world hints. The description adds that the tool loads the selected identity's cookie set and that subsequent calls act as that identity, disclosing persistence and scope. This goes beyond the annotations but does not cover potential error conditions.

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 consists of two short sentences. The first states the core purpose, and the second explains the mechanism and effect. Every word contributes value without redundancy.

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?

This is a simple tool with one parameter, an output schema, and annotations. The description adequately covers the main behavior and its implications for subsequent calls, which is the most important contextual information. No further details are needed.

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 fully documents the single parameter account_id with a description ('The stored account id to activate'), so the description adds no extra meaning. With 100% schema coverage, the baseline of 3 is appropriate.

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 states 'Switch which stored identity all tools act as', specifying a clear action and resource. It explains the effect on subsequent tool calls, distinguishing it from siblings like list_accounts or set_active_page.

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 clear context for when to use the tool—to change the active stored identity—and explains that subsequent calls use that identity's cookie set. It does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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