stellar_get_ledger_meta

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

With no annotations, the description carries the full burden. It discloses multiple behavioral traits: primary/fallback data sources, bounded responses with truncation metadata, and disk caching with TTL. This is good but could be more comprehensive (e.g., error handling, rate limits).

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?

Two sentences, no filler, and the core purpose is front-loaded. Every sentence is meaningful.

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?

Despite having no output schema, the description does not describe what the response contains (e.g., fields like sequence, hash, etc.). This is a significant gap, as the agent cannot infer the return structure from the description.

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%, so baseline is 3. The description adds context about truncation metadata for maxXdrCharsPerField but does not elaborate on ledgerSequence beyond the schema. The added value is marginal.

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 specifies the action ('Fetch closed ledger header metadata') and the primary/fallback sources, making the tool's purpose clear. It does not explicitly differentiate from siblings like stellar_get_transaction_meta, but the concept is distinct.

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 provides context on when the primary vs. fallback source is used, but lacks explicit guidance on when to choose this tool over alternatives or when not to use it. With many sibling tools, clearer usage directions would be helpful.

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