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

With no annotations, the description carries the behavioral burden and does well by stating it 'accepts no credentials, counter values, wallet or resource IDs, signatures, transactions, or raw provider responses' and 'does not run the provider tests itself.' It does not explicitly state whether the operation is read-only or has side effects, but the evaluative framing and input restrictions strongly imply a safe, non-mutating test.

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 sentences, front-loaded with the core purpose, then the alternative tool, then the distinguishing test scope and input constraints. Every sentence earns its place, and the structure is easy to scan.

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 tool with five required parameters, no annotations, and an output schema, the description is complete: it explains what the tool evaluates, how it differs from the sibling, what inputs are forbidden, and what it does not do. The output schema presumably covers return values, so no further return-format detail is needed.

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 the baseline is 3, but the description adds meaningful context by enumerating the tested behaviors (sequential cumulative limits, signed-but-unbroadcast accounting, ABI extraction, concurrent oversubscription, counter-reference failure, application serialization) that map to the observation `case` enum. It also reinforces the schema's rejection of unsafe inputs, adding value beyond the parameter descriptions.

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 opens with a specific verb and resource: 'Evaluate safe standardized observations from wallet policies that track prior or concurrent requests.' It clearly distinguishes this tool from its sibling by naming `wallet_policy_conformance` and contrasting the one-request controls it handles.

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 explicitly directs users to `wallet_policy_conformance` for one-request action shape, method, chain, token, recipient, amount, and function controls, while stating this tool is for stateful cumulative, concurrency, and serialization tests. This provides clear when-to-use and when-not-to-use guidance.

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