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

No annotations are present, so the description carries the burden of behavioral disclosure. It does establish that the tool is read-only and returns page content rather than navigation. However, it does not mention failure modes, authentication requirements, extraction caveats, or pagination behavior, leaving meaningful gaps.

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 tight sentences, each earning its place: the first defines the core purpose and gives examples, the second explains parameter format, and the third clarifies scope and output behavior. The most important information is front-loaded with no redundancy.

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 the low complexity of a one-parameter page reader, the description provides enough to select the tool, format the input, and anticipate the output. The main omissions are error handling and output format details, but the 'as text' and 'rather than its navigation' phrasing covers the essentials despite the absence of an output schema.

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?

The schema provides only a bare string parameter with no description, but the tool description compensates well by explaining that `path` accepts either a relative path like /themes/cyber or a full etfiq.com URL. This adds concrete format guidance and an example beyond the schema, though it still does not specify URL edge cases.

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 opens with a specific verb-resource pair ('Read ANY published ETFIQ page as text') and gives concrete page-type examples. It also explicitly distinguishes this generic tool from the specialized siblings by stating it covers 'everything the typed tools above do not cover.'

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 clearly conveys when to use this tool: for any published ETFIQ page, especially pages not covered by the other typed tools. It provides useful context for selection but does not explicitly name the alternatives or state when not to use it, so it falls just shy of a 5.

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