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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing about permissions, cost, determinism, or failure modes (e.g., what happens for an out-of-range sequence). The 'get_' naming weakly implies a read-only lookup, but that is inference from the name, not disclosure.

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?

It is a single short fragment with no filler or repetition, so it is maximally concise. However, brevity here tips into under-specification rather than efficient structure, and there is no front-loaded verb to orient the reader.

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 tool with one required parameter, no annotations, and no output schema, the description should explain what the inclusion data contains and how to obtain a valid seq. It fails to do either, leaving the agent without enough information to invoke the tool confidently or interpret the result.

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 single 'seq' parameter has 0% schema description coverage, so the schema supplies no meaning. The description's 'one ledger sequence' hints that seq is a ledger sequence number, which adds marginal value, but it omits valid ranges, expected source of the value, and error behavior for unknown sequences.

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 phrase 'Inclusion data for one ledger sequence' is a bare noun fragment that essentially restates the tool name 'get_ledger_proof' without a verb or clear statement that it retrieves a cryptographic inclusion proof. It conveys the resource (ledger inclusion data) and scopes it to a single sequence, but an agent gains little beyond the name.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling list is dominated by unrelated forum/wiki tools, so there is no obvious alternative to route to, but the description offers zero context about when this proof is needed (e.g., verification workflows).

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