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 structurally. The description adds one genuinely useful behavioral fact — results are ordered newest first — but says nothing about pagination behavior, default page size, or total counts, which matters for a ledger tool 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?

A single tight sentence that front-loads the resource and the ordering guarantee. Nothing redundant, nothing padded.

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 paginated ledger tool with no output schema and partially documented parameters, the description should explain page size defaults, pagination semantics, and what a ledger entry contains. None of that is present, so the agent has to probe.

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 only 33%: only orgId is documented (and its 'from org_list' hint lives in the schema, not the description). The description adds no meaning for limit or offset — no default limit, no max-page guidance, no statement of whether offset pagination is stable against new transactions arriving.

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 states a specific verb (Lists) and resource (organization wallet ledger) plus an ordering guarantee (newest first). However, it does not distinguish this from the sibling billing_transactions, which presumably lists the personal wallet ledger, leaving the agent to infer the scope difference from the name alone.

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 org_billing_get (balances), billing_transactions (personal ledger), or org_billing_topup. No exclusions or prerequisites are stated, so the agent must guess from naming conventions.

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