switch_account

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the need for confirmation ('Requires confirm=true') but does not disclose side effects, reversibility, or impact on the current session. Switching accounts is a state-changing operation, and the description fails to explain what happens to existing sessions or whether the switch is permanent. This lacks sufficient transparency.

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 extremely concise, consisting of two short sentences: 'Switch the active IG account. Requires confirm=true.' Every word earns its place, and the key information is front-loaded in the first sentence. There is no fluff or repetition, making it an example of effective minimalism.

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 that this is a state-changing tool with no annotations and an output schema (not detailed), the description is incomplete. It does not explain how to identify the target account, what 'default_account' does, or the consequences of switching. The single mention of confirm is not enough to fully guide an agent. A more complete description would cover account_id selection, default_account behavior, and potential side effects.

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 0%, so the description must elaborate on the parameters. It mentions 'confirm' as required, but ignores 'account_id' (which is the only required parameter) and 'default_account'. The schema provides basic types and defaults, but the description does not explain what these parameters mean or how they relate. This leaves significant ambiguity for the agent.

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 clearly states the tool's function: 'Switch the active IG account.' It uses a specific verb (Switch) and resource (active IG account), which distinguishes it from sibling tools like 'accounts' or 'session_details'. The purpose is unambiguous and directly matches the tool name.

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 specifies a required precondition: 'Requires confirm=true.' This tells the agent that the operation cannot succeed without setting the confirm parameter. While it does not explicitly mention alternatives or exclusions, the context is clear: use this tool when you need to switch the active account. The guidance provided is more than a vague hint.

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