remove_account

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

Discloses side effects: closes warm session, writes backup, leaves cookie file. No annotations provided, so description fully covers behavioral traits.

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?

Three concise sentences, front-loaded with main action and prerequisites. No fluff.

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?

Covers action, requirements, side effects, and recovery path. Lacks description of the account parameter, but output schema exists and annotations are absent, so burden is high but mostly met.

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?

Only the 'confirm' parameter is hinted (requires true). The 'account' parameter lacks any description; schema coverage is 0%, so description should compensate but only partially does.

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?

Clearly states the action (remove) and resource (account from config/accounts.json). Distinguishes from sibling tools like list_accounts or add_account by specifying the exact file and operation.

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?

Explicitly requires confirm=true, providing a usage condition. Does not mention when to use vs alternatives (e.g., set_account_active), but the prerequisite is clear.

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