stellar_get_account

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

No annotations exist, so the description carries the behavioral disclosure burden. 'Fetch' clearly signals a read-only operation, and listing the returned account fields gives useful context about the response content. However, it does not disclose behavior for nonexistent accounts, error responses, or any rate/auth constraints, so the transparency is partial.

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 one compact, front-loaded sentence with no filler words. It states the action, resource, and key output contents efficiently, earning its place entirely.

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 simple one-parameter read tool, the description is mostly sufficient: it names the key return fields and clearly indicates a non-mutating operation. Since there is no output schema, the field list partially compensates, but it still omits edge-case behavior such as what happens when the account does not exist.

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 input schema covers 100% of the single parameter, publicKey, with its own description, so the baseline is 3. The tool description adds no additional semantic detail about the parameter beyond what the schema already states.

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 uses a specific verb ('Fetch') and identifies the resource ('account details') plus concrete elements: balances, signers, flags, and calculated minimum balance. It is clearly distinct from sibling tools like stellar_get_account_history, which focuses on historical data, while this tool returns the account state snapshot.

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 a clear use case—fetch current account state—but provides no explicit guidance about when to choose this tool over siblings or when not to use it. It does not mention alternatives such as stellar_get_account_history for historical queries, so the usage context is mostly inferred.

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