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

No annotations are supplied, so the description carries the burden. It implies read-only behavior by describing published data and specifies the content returned, but it does not state side effects, required access, error handling, or output structure.

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?

Single sentence, front-loaded with the core scope ('Everything ETFIQ publishes about one fund') followed by useful granularity. No filler.

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 lookup, the description is mostly complete: it tells the agent what content to expect (issuer, desk, figures with source/as-of, verdict). However, with no output schema and no guidance on not-found or malformed ticker behavior, there is a small but real gap.

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 0% and the description never mentions the `ticker` parameter explicitly; 'one fund' only weakly implies that the ticker identifies the fund. No format, examples, or constraints are provided for the parameter.

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 action scope — all ETFIQ-published data for one fund — and enumerates content categories (issuer, desk, figures with source/as-of, verdict). This clearly distinguishes it from multi-fund siblings like etf_rankings or etf_screen.

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 implies the tool is for single-fund deep-dive lookups ('one fund'), but it never names sibling tools or gives explicit when-to-use vs when-not-to-use guidance. An agent would have to infer that etf_holdings or etf_theme are more targeted alternatives.

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