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

Beyond the readOnly/idempotent annotations, the description adds valuable behavioral details: results are sorted largest first, net assets are accompanied by source and date, fees are percentages not basis points, and funds without published size are handled as a separate no_size_figure bucket rather than treated as small.

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 tight sentences with no filler. It front-loads the core behavior, then adds usage guidance, units, and an important edge case in a logical order.

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 no output schema, the description reasonably conveys return contents and a key edge case. It does not explain limit behavior, pagination, or the exact semantics of desk/issuer, but for a moderate-complexity read-only screen tool it is mostly complete.

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 0%, so the description must compensate; it does clarify max_fee_pct unit semantics and the min_assets_usd missing-size behavior. However, desk, issuer, and limit remain unexplained, leaving the agent to infer their meaning from parameter names alone.

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 clearly states the tool's purpose: it returns every fund matching filters, sorted largest first, with net assets and source/date. It also distinguishes itself from repeated-search workflows by calling out "find me all X" questions, making it easy to separate from sibling tools like etf_search.

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 gives an explicit when-to-use rule: "Use for 'find me all X' questions rather than repeated searches." It does not name a specific sibling alternative, but the contrast with repeated searches is clear enough to route an agent appropriately.

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