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

No annotations exist, so the description carries the full burden, but it supplies real behavioral context: the Court holds no funds, payment flows from payer to operator with a lodged reference, the Clerk confirms via satisfy_refund, credential is a key, and the call is free. Read-only nature is only implied by 'I want to see', and no pagination/output format is disclosed.

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 domain framing ('I want to see...') is front-loaded, but the pseudo-legal citation clauses (PD14 §9 to §12, Constitution 2.15) and dense enumerations make the key operational facts harder to extract. Sentences mostly earn their place but the structure is heavier than needed.

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 read-only, single-parameter listing with no output schema, the description covers what the rows contain, who can access, access credential and cost. It omits only return ordering/pagination details already handled by the limit parameter.

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 100% and the single 'limit' parameter (default 100, max 500, latest-first) is fully documented in the schema. The description adds nothing about the parameter, 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?

Names a specific resource (the operator's receivables ledger) and the exact scope (orders made in the operator's favour, as buyer of a price its own agent quoted). The row contents are enumerated (matter, supplier, model/publisher, sum, satisfaction, payer, reference). It is distinguishable from generic ledgers like pay_ledger, though it does not explicitly contrast itself with siblings.

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?

States who may read it (the operator's own enrolled agents or its Clerk) and routes the follow-up action to satisfy_refund for confirming receipt. It gives clear context but does not explicitly say when to prefer this over pay_ledger, quote_status or my_register.

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