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

No annotations are provided, so the description carries the burden for transparency. It clearly implies a read-only listing operation, but it does not explicitly state that it does not modify data, nor describe output format or any potential side effects. For a zero-parameter listing tool, this is adequate but could be more explicit.

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 zero waste. The core purpose and usage guidance are front-loaded, and each sentence earns its place. It is concise without omitting essential context.

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 no parameters and no output schema, the description fully explains what it returns (section list with page counts) and when to use it. No further details are missing for an agent to invoke it correctly.

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?

There are no parameters, so schema coverage is 100% trivially. The description adds no parameter-specific details (there are none), but the baseline for zero parameters is 4 because there is nothing to document.

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 lists ETFIQ publication sections with page counts, and explicitly says 'Start here when the question is not about one fund,' distinguishing it from fund-specific sibling tools. This gives a specific verb ('start here'), resource (ETFIQ sections), and a clear differentiator.

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 provides an explicit when-to-use condition ('when the question is not about one fund') and implies that fund-specific tools are for single-fund queries, but it does not name specific alternatives like etf_profile or etf_holdings. Still, the guidance is clear and actionable.

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