accounts_remove

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

With no annotations, the description carries the full burden. It does disclose one genuinely useful behavioral trait: the .p8 credential file on disk is preserved, bounding the blast radius of a destructive-sounding operation. However, it says nothing about reversibility, whether removal is refused for the active account, or any side effects, so the destructive profile remains only half-specified.

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?

Two sentences, the core action front-loaded and the important caveat immediately after. No filler, no restatement of the tool name.

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 one-parameter local-registry tool with no output schema, the description covers the action and the key non-effect on disk. It still leaves gaps an agent would want: identifier format and any precondition about the currently active account.

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 single required 'name' parameter has 0% schema description coverage, and the description never states what form that name takes (account label, email, team ID) or how it matches a registry entry. The text implies an account is identified but adds no meaning beyond the bare schema.

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 gives a specific verb+resource ('Remove an account') scoped to 'the local registry', and the .p8 caveat sharpens that scope. It is clearly distinguishable from accounts_add/accounts_switch/accounts_list without opening a schema, though it never names a sibling explicitly.

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?

There is no guidance on when to remove an account versus switching away from it or updating it, and no prerequisites (e.g., whether the account must be inactive). The 'local registry' phrasing implies the domain but does not route the agent among the accounts_* siblings.

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