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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful context beyond them: the data is a snapshot of a public page, it is not investment advice, and each successful call costs $0.002 via x402 while failures are free. It does not discuss freshness cadence or rate limits, but the cost and snapshot caveats are substantive.

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 front-loaded with the resource and returned fields, then adds snapshot and payment caveats. It is compact and mostly waste-free, though the 'not investment advice' clause is boilerplate rather than operational guidance.

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?

Given an output schema exists, the description need not explain return structure. It covers the data source, snapshot nature, and pricing model, which are the main non-schema facts an agent needs; only selection guidance against alternatives is missing.

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%, and the single `limit` parameter is already documented as 1–50 with a default of 10. The description adds no additional meaning about how the limit affects output or pagination, so 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 the exact resource (Dataroma superinvestor portfolios) and enumerates the returned fields: manager/firm name, portfolio value, stock count, and top-holdings tickers. It also identifies the source table, which is enough for an agent to recognize this as a portfolio-snapshot lookup rather than a generic finance tool.

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 explicit guidance on when to use this tool versus alternatives such as pitchbook or SEC adviser data, nor any exclusions (e.g., that it is not individual 13F filing detail). Usage is only implied by the purpose statement.

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