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

The readOnlyHint annotation already declares this as a safe read operation, so the description doesn't need to restate that. It adds some context about the private nature and scope of the data (ledger entries and funding provenance), but it doesn't disclose pagination behavior, ordering, or what exactly is returned.

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 a single sentence that front-loads the action ('Read') and uses every word to convey meaning. There is no fluff, repetition, or unnecessary detail.

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 read tool with one optional parameter and a readOnlyHint annotation, the description gives adequate scope context. However, with no output schema and no explanation of how offset works or what the returned ledger data looks like, an agent may still be uncertain about pagination and return format.

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 schema has one parameter, offset, with a default of 0 but no description; schema description coverage is 0%. The description does not explain offset or pagination semantics, leaving the agent to infer meaning solely from the parameter name. Since there is only one parameter, the gap is modest, but the description still fails to compensate for the missing schema documentation.

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 clearly identifies the verb ('read'), the resource ('private ledger entries'), and a second associated resource ('funding provenance'). It is specific enough to distinguish itself from most sibling tools, though it does not explicitly differentiate itself from read_wallet or other read_* tools.

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 guidance on when to use this tool versus alternatives like read_wallet or get_my_trust. The description only implies usage for viewing ledger entries, with no exclusions, prerequisites, or context about when it is the right choice.

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