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

There are no annotations, so the description must carry the behavioral burden. It communicates read-only intent ('List') and a 'recent' temporal scope, but it does not clarify ordering, pagination, or the meaning of 'FREE (operator)'. These omissions leave some behavioral uncertainty, though the core listing behavior is clear.

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 two sentences with no wasted words. The main action is front-loaded, followed immediately by usage guidance. It earns a top score for minimalism and clarity.

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 optional-parameter list tool, the description covers purpose, parameter hints, and usage differentiation. It doesn't explicitly describe the return format or clarify what 'FREE (operator)' means, but given the low complexity and complete schema, the essential information for correctly invoking the tool is present.

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 100%, and both parameters already have clear descriptions in the input schema. The description adds only a small amount of nuance by mapping the in/out/markup values to ledger directions, but it does not materially exceed what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb ('List') and resource ('recent ledger rows') and immediately clarifies the optional in/out/markup directions. It also distinguishes the tool from siblings by naming get_pnl and get_paywall_status with the specific scenarios they serve, leaving no ambiguity about what this tool does.

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?

Explicit routing guidance is provided: 'Prefer over get_pnl when you need individual settlements; prefer over get_paywall_status when auditing history, not current prices.' This directly tells the agent when to choose this tool over alternatives, which is exactly what the dimension asks for.

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