Switch Account

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

With no annotations, the description bears full responsibility for disclosing behavior. It only states 'Switch' but does not mention side effects (e.g., changing global state, affecting other sessions), permission requirements, reversibility, or what the operation returns. This is minimal transparency for a mutating operation.

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?

A single, front-loaded sentence with no unnecessary words. It is appropriately sized for a simple tool, but it lacks a structured breakdown or additional helpful context that could be packed into the same space without harming conciseness.

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 the presence of an output schema, return values are covered, but the description omits usage guidance and behavioral details. For a state-changing tool with no annotations and several related siblings, the description is insufficient for an agent to select and invoke the tool correctly without ambiguity.

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 description coverage is 100%, with the parameter 'account' described as 'Account ID or alias to switch to'. The description adds no additional meaning beyond the schema, meeting the baseline of 3 for high coverage. No extra context about valid formats or accepted aliases is provided.

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 'Switch the active AWS account context' uses a specific verb ('switch') and resource ('active AWS account context'), making the core function clear. It distinguishes from siblings like switch_environment and select_profile by focusing on account context, though it does not explicitly differentiate itself from assume_role or list_accounts.

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?

No guidance is provided on when to use this tool versus alternatives such as assume_role, select_profile, or switch_environment. The description does not mention prerequisites, use cases, or exclusions, leaving the agent to infer when 'switch_account' is appropriate.

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