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

Annotations already cover read-only and open-world behavior, and the description adds genuinely new context: the source is a live scrape of a public page ('snapshot'), the cost is $0.002 USDC per successful call via x402 on Base, Solana or Arc, and failed calls are not charged. That payment/cost disclosure is exactly the kind of detail annotations cannot carry. It omits data freshness and any rate limiting, keeping it off a 5.

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?

Two sentences with no filler: contents first, then caveats and pricing. The dense field enumeration is front-loaded and scannable. Minor cost is that the payment clause is packed into the same sentence flow, but nothing is redundant.

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 one-parameter read-only snapshot with an output schema, the definition covers what it returns, where it comes from, its caveats, and its price. The remaining gap is freshness/recency of the underlying page snapshot and total coverage of the manager table, which an agent budgeting calls would want.

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% for the single 'limit' parameter, which documents range 1-50 and default 10, so the schema carries the semantics. The description adds nothing about limit behavior (e.g., whether 50 is the full manager roster), so the baseline 3 applies.

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 a specific verb+resource ('read from Dataroma's public manager table') and enumerates exactly what each row contains: manager and firm name, portfolio value, stock count, and top-holding tickers. An agent knows precisely what this returns. It stops short of naming a sibling it is not (e.g., finance_pitchbook_investors or finance_sec_iapd), but the unique source makes the scope unambiguous.

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?

There is no when-to-use guidance: nothing says when to pick this over the adjacent investor-holdings tools listed as siblings, nor what happens at the default limit of 10. The only usage-adjacent statements are 'Snapshot of the public page' and 'not investment advice,' which set expectations about freshness and liability rather than selecting conditions.

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