stellar_fund_account

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

The description discloses the action but lacks details on behavioral traits such as possible rate limits of Friendbot, whether the account must be new, or what happens if the account already has funds. No annotations compensate for this gap.

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?

The description is a single sentence of 12 words, achieving maximum conciseness while conveying the essential purpose. It is front-loaded with the key information.

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?

Given the simplicity of the tool (one parameter, no output schema), the description adequately covers the purpose. It could mention that it only works on testnet or the Friendbot service, but overall it is sufficient.

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 coverage is 100% with one parameter (publicKey) described clearly. The description adds context (amount and method) but does not significantly enhance understanding beyond the schema's existing documentation.

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 (fund), resource (Stellar testnet account), amount (10,000 testnet XLM), and method (Friendbot). It distinguishes itself from siblings by specifying testnet and Friendbot.

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 description implies usage for funding testnet accounts but does not explicitly state when to use this tool versus alternatives like stellar_submit_payment or stellar_get_account. No exclusions or prerequisites are mentioned.

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