accounts_remove

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

The description discloses one important behavior (does not delete the key file), which is not shown in annotations or schema. However, it omits other behavioral details such as idempotency, error handling, or permission requirements.

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?

Extremely concise: one sentence for core purpose, one for key behavioral note. No redundant information. Front-loaded and efficient.

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 simple tool with one parameter and no output schema or annotations, the description is too sparse. It lacks information about error cases, what happens if the account doesn't exist, and the meaning of 'name'. Additional context is needed for safe usage.

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?

The sole parameter 'name' has no schema description (0% coverage) and the tool description adds no explanation about its format, expected values, or constraints. The parameter name is intuitive, but for a required parameter, more detail would help.

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 action (remove an account) and the scope (from local registry), with an explicit clarification that it does not delete the key file. This distinguishes it from potential misunderstandings but could be more specific about what 'local registry' means.

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?

No guidance on when to use this vs alternatives like accounts_update or accounts_switch. The description does not mention scenarios, prerequisites, or when not to use the tool.

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