settle_all_ai_rewards

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

Annotations only declare readOnly=false and idempotent=false; the description adds concrete behavior: validating eligible receipts, submitting one Merkle-root publication and one claim transaction per batch, and requiring host/user confirmation policy. It also explains bounded execution, which is valuable beyond the structured annotations.

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 four dense sentences with no filler. Each sentence earns its place: usage trigger, parameter bounds, transaction behavior, and alternative routing. It is front-loaded and 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 two self-describing parameters and no output schema, the description covers trigger conditions, exclusions, batching semantics, transaction details, confirmation responsibility, and sibling differentiation. No critical operational gap remains for an agent deciding whether and how to invoke it.

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% with defaults and bounds already documented, but the description adds operational meaning: batchSize represents eligible receipts per batch, maxBatches bounds total settlement work, and the per-batch transaction count clarifies the effect of each parameter. This goes beyond the schema's basic 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 names the operation as settling all eligible local receipts and submitting Base transactions per batch, making the tool's scope explicit. It also distinguishes itself from settle_ai_rewards, so an agent can tell them apart without opening the sibling schema.

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?

It states a precise trigger condition ('claim my AIPOU' or 'settle all pending AIPOU'), explicitly says not to use it for a status check, and names settle_ai_rewards as the alternative for a single limited batch. This gives 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.