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

With no annotations provided, the description carries the full burden and does so excellently. It discloses that internal transfers have no transaction hash, that the journal is append-only and never truncated, and that paging uses a `before` sequence number. These are critical behavioral traits beyond what the schema reveals.

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 three dense sentences, front-loaded with the most important fact (no transaction hash), and every sentence earns its place. It efficiently covers purpose, behavioral traits, and usage context without fluff.

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?

Given the tool's simplicity (a history list), lack of output schema, and absence of annotations, the description provides all necessary context for an agent to select and invoke it correctly. It covers the 'why' (verify/dispute internal payments), the 'what' (full untruncated history), and the 'how' (paging with `before`).

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%, so baseline is 3. The description adds meaningful semantics for the `before` parameter by explaining it is a seq number for paging and emphasizing that the tool never truncates results, which enriches the schema's bare 'return entries with seq below this'.

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 explicitly states the tool provides the full, untruncated netting history for an address, and explains that it records internal transfers with no transaction hash. This clearly distinguishes it from sibling netting tools by emphasizing it is the only record for such transfers.

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 a clear when-to-use directive: 'Use this when a user asks to verify or dispute an internal payment, since there is no chain to check.' It also provides paging guidance with `before`, making the invocation context explicit.

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