stellar_keys_remove

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

No annotations provided, so the description carries the full burden. It says 'Remove' but doesn't disclose whether deletion is permanent, whether the key can be recovered, or what happens to config state. A destructive operation of this kind needs that context.

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 words, perfectly front-loaded and waste-free. Brevity here edges toward under-specification rather than padding, but structure is clean.

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?

Two-param mutation tool with no annotations, no output schema, and a description far too thin to explain consequences. An agent knows it removes an identity but not what that entails.

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 100%, so the schema already documents both 'name' and 'configDir' adequately. Baseline 3 applies; description adds nothing beyond the resource name.

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?

States a specific verb (Remove) and resource (identity), which is clear enough. But it's minimal and doesn't distinguish from sibling stellar_keys_secret or stellar_keys_use, nor mention it removes keys from stored config.

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 when-to-use guidance, no prerequisites, no warning about irreversibility, and no routing to sibling tools like stellar_keys_list to find names. Siblings stellar_keys_add/generate exist, implying this is the inverse, but that's inferred not stated.

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