remove_account

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

Since no annotations are provided, the description fully carries the burden. It discloses the operation is ONE-WAY, deletes from AccountStore and OS keychain, and specifies return values and error conditions. This is thorough and honest.

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 informative but could be more streamlined. It includes usage examples, input details, and returns in a natural flow, but some redundancy exists (e.g., repeating 'ONE-WAY'). Still, it is not overly verbose.

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 no annotations or output schema, the description covers the essential aspects: irreversible operation, target, return values, and error case. It could mention prerequisites like user authentication, but overall it is comprehensive enough for a single-parameter tool.

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%, so baseline is 3. The description adds value by providing format examples (e.g., 'bybit:UNIFIED') and reiterating the one-way nature, which goes beyond the schema's simple description.

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 it deletes an account and its credentials, and provides specific example phrases like 'remove the Bybit account' that cue the agent. It distinguishes from sibling tools like remove_custom_token by focusing on accounts.

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 explicit when-to-use guidance by listing user queries. It mentions the Settings UI requires confirmation, implying appropriate timing. However, it does not explicitly contrast with alternatives like remove_custom_token or note when not to use.

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