stellar_keys_add

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

No annotations are provided, so the description carries the full burden. It is a mutation tool (creates/stores a keypair) yet says nothing about permissions, whether it overwrites an existing identity, or that it triggers interactive prompts for secretKey/seedPhrase. The interactive nature is only implied by the schema, not the description.

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?

A single short phrase, front-loaded with the verb and resource. The parenthetical is terse to the point of being cryptic about the ledger/secure-store options but costs little.

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?

A six-parameter creation tool with no annotations and no output schema needs the description to explain side effects, prompting, and storage behavior. The description supplies none of this, leaving significant gaps for safe invocation.

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 each of the six parameters is already documented in the schema. The description adds no extra meaning (e.g. how publicKey vs secretKey vs seedPhrase interact, or what configDir accepts), so baseline 3 applies.

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 (add) and resource (identity/keypair), with a parenthetical hinting at the storage backends. However it does not differentiate itself from close siblings like stellar_keys_generate or stellar_keys_use, leaving the agent to infer the distinction.

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 indication of when to use this versus stellar_keys_generate, stellar_keys_use, or stellar_keys_secret. No prerequisites, no note about whether an identity must already exist or whether this overwrites one.

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