set_default_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 states the immediate effect (setting the default account) but omits critical details such as persistence, scope (session vs global), validation of the account, and whether prior defaults are overwritten. This is a meaningful gap for a mutation tool.

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, focused sentence with no superfluous words. It front-loads the verb and resource, making it immediately understandable. Perfect 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?

The description covers the basic purpose but lacks workflow context, such as referencing list_accounts to select a valid account, or clarifying whether the default persists across sessions. Given the tool's simplicity and the presence of an output schema, it is minimally adequate but leaves operational questions unanswered.

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%, and the description provides no additional meaning for the 'account' parameter. It does not specify whether the account is an ID, name, or email, nor how to discover valid values (e.g., via list_accounts). The parameter remains ambiguous.

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: 'Set the default account used when no account is specified in other tools.' It uses a specific verb ('Set') and resource ('default account'), and explicitly distinguishes it from sibling tools by explaining its role as a global setting affecting other 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 provides clear context on when to use the tool—when a default account is needed for other tools. It does not explicitly mention alternatives or exclusions, but the purpose is unambiguous and sufficient for a simple setter, earning a 4.

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