stellar_keys_fund

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 usefully discloses the test-network restriction, which is a meaningful behavioral constraint, but says nothing about the funding mechanism (e.g., friendbot), idempotency, rate limits, or what changes on the network as a result.

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 sentence with zero waste and the key constraint front-loaded. It is arguably too terse rather than padded, but it is structurally 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?

For a mutation-style tool with 7 parameters, a nested object, no annotations, and no output schema, the description omits critical context: where funds come from, whether the call can fail on live networks, and what the caller should expect. It is incomplete for the tool's complexity.

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% with 7 documented parameters, so the schema already explains each field. The description adds no parameter-level meaning beyond that baseline.

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 ('Fund') and resource ('identity') and scopes it to a test network, which is more specific than the bare name. It does not differentiate itself from sibling key tools like stellar_keys_generate or stellar_keys_add, but the purpose is unambiguous.

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 phrase 'on a test network' implies this only applies to test networks, giving an implicit usage condition. However, it names no alternatives (e.g., what to do on mainnet), no prerequisites, and no when-not-to-use guidance.

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