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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the bar is low, yet the description adds substantial operational context the annotations cannot express: $0.03 per call over x402 on Base, an x-credit-token header for unlimited calls, one free call/day, and no API key required. It also explains the multiplier settlement mechanic and that lenders pause a reserve during application.

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?

Purpose is front-loaded in the first clause, and the following sentences each carry real information about the multiplier mechanic, coverage scope, and pricing. It runs slightly long and 'Not financial advice' is filler, but nothing structurally buries the lead.

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?

With an output schema present, return values need not be explained, and the annotations carry the safety profile. What remains an agent needs — what the tool covers (all listed tokenized stocks plus ERC-8056 schedules), the optional wallet filter, the payment model, and why the data is non-obvious — is all 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 there is a single optional wallet parameter, so the baseline is 3. The description's 'which touch that wallet's holdings' largely restates the schema's 'Wallet to intersect with holdings (optional)' rather than adding format, address-chain, or edge-case semantics.

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 states a specific verb and resource: it lists announced dividends and splits across Base's tokenized stocks, with optional wallet intersection. It is far more specific than a generic 'corporate actions' label, though it never names an overlapping sibling such as rwa_dividend_feed or tokenized_stock_price, leaving the agent to infer the boundary from scope alone.

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 gives clear context for when this matters: a naive balanceOf reader is silently wrong because settlement moves the multiplier, and Coinbase announces actions on chain days ahead. That is strong 'why/when' framing, but there is no explicit when-not guidance or named alternative tool for adjacent questions like current price or holdings.

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