Stellar network health and fees

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld. The description adds useful disclosure in the form of the exact returned metrics, but says nothing about freshness/latency, rate limits, or whether the data is a point-in-time snapshot.

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 dense sentence, front-loaded with the primary subject (latest Stellar ledger) and then fee levels. The parenthetical field lists are compact and earn their place, though the sentence is somewhat list-heavy.

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?

No output schema exists, so the description carries the burden of describing return values — and it does so thoroughly by enumerating both ledger and fee fields. For a zero-parameter read-only tool, that is nearly sufficient; only data freshness/scope caveats are missing.

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?

With zero parameters there is nothing for the schema to document, so the baseline is 4. The description instead spends its space describing the returned fields, which is the relevant semantic information for a no-arg tool.

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 names the specific resource and enumerates the content returned: latest ledger fields (sequence, age, transactions, failure rate, protocol version, base reserve) plus fee levels. This makes clear it is a network-health snapshot, distinct from siblings like stellar_account or stellar_orderbook, though there is no explicit verb or direct sibling contrast.

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?

There is no statement of when to call this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer from the field list that this answers questions about ledger state or fee conditions.

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