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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds genuinely useful behavioral detail beyond that: it returns page *content*, not navigation chrome, which tells the agent what kind of payload to expect. It stops short of noting format details like truncation or handling of unpublished paths.

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?

Three sentences, zero filler, with the core function and output shape front-loaded before the path-format detail. Every clause contributes either scope, differentiation, or input format.

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 one parameter, no output schema, and full annotation coverage, the description supplies what an agent needs: what it reads, what input shapes it accepts, and that it returns content rather than navigation. Minor gaps remain around response size/format and failure modes for unpublished pages.

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 single parameter is entirely undocumented in the schema, so the description carries the burden. It does so reasonably well by giving an example value (/themes/cyber) and stating a full URL is also accepted, though it does not specify error behavior for invalid or unpublished paths.

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?

States a specific verb+resource ("Read any published ETFIQ page as text") and enumerates the page classes it covers (theme hub, ranking, comparison, issuer, methodology, dated study). The clause about reaching all 40,000 pages that the typed tools do not cover explicitly differentiates it from siblings like etf_profile or etf_theme.

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?

Provides clear usage context: it is the catch-all reader for anything the typed tools miss, and it accepts either a path or a full etfiq.com URL. It does not explicitly compare against the sibling find_page, which is the closest alternative for locating content, so routing guidance is slightly incomplete.

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