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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's contribution is the interpretive framing: states are Supports/Mixed/Challenges/Not enough data and are explicitly 'never a call to buy, sell or hold', plus every answer carries a disclosure and per-seat source links. That is genuinely useful context beyond the structured fields, though pagination/return shape detail is absent.

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 paragraph is front-loaded with what the tool is, then layers in the state vocabulary, the disclaimer and the seat links. It is dense but every clause carries information; the only mild redundancy is restating the state names twice ('each with its state' and 'each criterion's state').

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 must sketch the return payload and does: per-seat state, measurable coverage, per-criterion states, an attached disclosure, and a link per seat. What remains unclear is the form of 'how much of the seat could be measured' (count, percentage, enum) and behavior for an invalid ticker.

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 is a single required parameter with 100% schema description coverage ('One fund's ticker, such as JEPI'), so the schema carries the burden. The description only reinforces the single-fund scope ('reads one ETF') and adds no format, casing or lookup semantics. Baseline 3 is appropriate.

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 resource and verb-equivalent: 'how each seat of the IQ Investment Committee reads one ETF', enumerating the 11 philosophy seats plus the ETFIQ Skeptic and the per-seat state model. An agent can tell exactly what comes back. It does not, however, position itself against nearby siblings such as etf_scorecard, etf_promise or etfiq_sections, which also produce per-ETF judgements.

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?

Usage is implied rather than stated — an agent infers 'call with a ticker when you want the committee's per-seat verdicts'. The one real cue is that each seat links its own page carrying the published source and thresholds, hinting at a follow-up call, but no sibling is named and no when-not condition is given.

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