rustchain_ledger

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

With no annotations provided, the description carries the full behavioral burden and delivers almost nothing: it does not state that this is a read-only operation, what 'recent' means (ordering, window, cursor), how pagination works, or whether results are address-scoped or global. An agent cannot predict the result set from this text.

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 compact sentence with no filler and the resource front-loaded. It is efficient, though its brevity is partly under-specification rather than genuine concision.

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 no annotations and no output schema, the description should explain ordering, scope, and return shape, but it does none of these. The agent is left guessing what a 'transaction' record contains and whether the list is global or tied to a specific account.

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?

There is a single optional 'limit' parameter with 100% schema description coverage, including its default of 10. The description adds no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Get') and resource ('ledger transactions') with a scope qualifier ('recent'). It is clear what the tool returns, but it does nothing to distinguish itself from siblings like rustchain_transfer or rustchain_balance, which an agent might also consult for ledger-related data.

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 gives no guidance on when to use this over rustchain_transfer, rustchain_balance, or rustchain_epoch. There is no stated condition, no alternative named, and no mention of prerequisites such as authentication or address filtering.

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