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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — results are ordered newest first — but says nothing about pagination behavior, default page size, or whether the ledger is truncated, which matters for a list endpoint with limit/offset.

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?

One sentence, front-loaded with the verb and resource, with no filler. It is efficient but borders on under-specified for a paginated list endpoint — the brevity comes at the cost of the pagination detail an agent needs.

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-only list tool with annotations covering safety and no output schema, the bar is modest, and the ordering hint helps. Still missing is any signal of ledger scope (personal vs org) and pagination/default-limit behavior, which the 0%-coverage schema cannot supply.

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 description coverage is 0%: neither 'limit' (1-100) nor 'offset' (>=0) is documented in the schema, and the description does not compensate. Only the ordering is implied; the agent gets no statement of the default page size, max page size, or how offset interacts with the newest-first ordering.

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 and resource ('Lists the wallet ledger') plus an ordering guarantee ('newest first'), so the agent knows exactly what comes back. It does not, however, distinguish itself from the similarly named sibling org_billing_transactions or from billing_get, leaving the agent to infer which scope each covers.

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 at all — nothing says whether this is the personal wallet ledger versus the org ledger in org_billing_transactions, nor when to prefer billing_get or topup_lookup. The agent must guess from the name alone.

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