setup_select_account

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

With no annotations, the description carries the transparency burden. It hints at session validation but doesn't specify what 'validate' means, failure modes, or side effects. It's adequate for a simple setup step but lacks detail on what gets modified or checked.

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 a single sentence, front-loaded with the action and resource. It's concise and includes the key usage hint without extra fluff. Slightly more detail on validation could help, but it's appropriately sized.

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 single-parameter tool with full schema coverage and no output schema, the description covers core usage. However, it doesn't mention expected outcomes, error handling, or what happens if the session is invalid, leaving some gaps for a tool that validates something.

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 100% with a clear description for account_index. The description adds little beyond the schema, but since the schema is already explicit and the tool has only one parameter, a 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 clearly states the tool selects a Figma account and validates the session, with a specific verb-resource pair. It distinguishes from siblings by naming setup_extract_cookies as a prerequisite, though it doesn't explicitly contrast with other setup 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 instruction to call after setup_extract_cookies provides clear sequencing context, implying this tool depends on prior cookie extraction. It doesn't mention when not to use it or alternatives, but the dependency guidance is useful for correct invocation.

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