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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds valuable provenance: data is sourced from the matching iShares ETF's daily holdings file as a free point-in-time proxy, and notes that official index publishers don't release this data for free. It does not discuss data freshness beyond "daily" or error behavior, so a 4 rather than 5.

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?

Front-loads the core purpose, then adds provenance and exclusions. The parenthetical rationale is dense but earns its place. Slightly long for a single sentence, but overall well-structured and without redundant 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?

With no output schema, the description explicitly lists the returned fields (ticker, name, GICS sector, weight). Combined with rich annotations and 100% schema coverage, it gives an agent everything needed to call the tool correctly and understand its data lineage.

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 description coverage is 100%: the enum values, limit behavior, offset paging, and sector substring filter are all fully documented in the schema. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline of 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?

States a specific resource (current constituents of a major US or developed-markets equity index) with the exact fields returned (ticker, name, GICS sector, weight), and explicitly distinguishes itself from ishares_etf_holdings by excluding cash, collateral, and futures positions. An agent can immediately tell what it does and how it differs from the nearest sibling.

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 concrete example questions it answers ("what's in the S&P 500 right now", "top holdings of the Russell 2000 by weight"), and explicitly names the alternative tool (ishares_etf_holdings) for the excluded asset types. Both when-to-use and when-not-to-use are covered.

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