get_etf_full_holdings

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

With no annotations, the description carries the behavioral burden. It discloses the exact data source, update cadence and lag, the fact that positions come from official filings rather than a third-party feed, and the required credential setup. It does not cover failure modes or rate limits, but for a read-oriented data tool the disclosed behavior is substantial.

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 description is three tight sentences: a scoped statement of what the tool returns, a compact list of derived metrics, and two critical caveats (freshness and authentication). Every sentence earns its place, with the most identifying detail front-loaded.

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?

The description is quite complete for a simple two-parameter read tool with no output schema: it names the source, the input required, the output contents, data staleness, and authentication. The only minor gap is the slight ambiguity between 'every position' and 'top positions,' which the top parameter and context help resolve.

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?

Input schema coverage is 100%, so symbol and top are already documented, including the default and range for top. The description adds context that the listed positions are weighted and that concentration metrics are included, but it does not materially extend the parameter semantics beyond what the schema already provides.

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 clearly identifies the operation: retrieving every ETF position from the latest SEC Form N-PORT filing, and enumerates what is returned (top positions by weight, concentration metrics, breakdowns). It distinguishes itself mainly by source ('not Yahoo') and 'full' holdings, but it does not explicitly name or contrast the sibling get_etf_holdings, so sibling differentiation is only implicit.

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 gives useful context on when the data is appropriate: quarterly and about 60 days behind, sourced from SEC N-PORT rather than Yahoo. It also states the SEC_USER_AGENT prerequisite. However, it never explicitly says when to choose this tool over get_etf_holdings or other ETF siblings, so usage guidance is implied rather than stated.

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