select_account

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

Annotations already mark this as non-read-only and non-destructive. The description adds that it changes the active ad cabinet and that verification is recommended afterward. It does not go into side effects or error behavior, but with annotations covering the safety profile this is a minor gap.

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 compact and front-loaded: the main action is the first sentence, verification steps follow, and the only parameter is documented in one line. No unnecessary words.

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 one-parameter state-switch tool with annotations and an output schema, the description is nearly complete. It names the parameter source and the recommended follow-up calls. It could mention what response to expect or what happens to the current session, but the output schema likely covers the response.

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 0%, so the description carries the burden. It adds 'From list_accounts', which tells the agent exactly how to source owner_id—meaningful provenance beyond the schema's generic 'Owner Id' label. It could further explain what owner_id represents, but the purpose statement largely covers that.

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 opens with a specific verb and resource: 'Switch the active ad cabinet.' This clearly identifies the state-changing nature and distinguishes it from read tools like list_accounts/get_account. It does not explicitly name a sibling in the purpose, but the action is unique among the provided tools.

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 contextual sequencing: switch first, then check_session / get_account, and it states where owner_id comes from (list_accounts). This communicates when to call it, though it does not explicitly state when not to use it or name alternatives.

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