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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered. The description adds value beyond them by naming negative scope ('Issuer-trained short-interest forecasts and squeeze scores are not ETF analytics') and by flagging the sibling-fund caveat for the SEC registrant tools.

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?

Purpose is front-loaded in the first sentence and every clause is functional, but the middle routing sentence is a long run-on enumerating many siblings that is dense to parse. Efficient overall with no filler, though structure could be tighter.

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?

For a single-ticker, closed-world read tool with no output schema, the definition covers purpose, scope, sibling routing, and negative boundaries. Nothing an agent needs to call it correctly is missing.

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?

Only one parameter with 100% schema description coverage, so the schema fully documents 'ticker' (including SPY/VOO/IVV examples). The description reinforces 'this same exact ETF ticker' but adds no format or syntax detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 and resource ('Get ETF settled performance, SEC assets, allocation and top holdings') and explicitly differentiates from the closest sibling: 'GetEtfHoldings instead returns investments inside the ETF.' An agent can distinguish the two without opening either schema.

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?

Explicitly routes the agent to alternatives by data need (GetStockPrices/GetLatestClosingPrices for prices, GetLiveQuote for intraday, option tools, short interest, 13F exposure, dividends, congressional trades). It also warns which tools return the wrong entity scope (ListFilings/SearchDocuments may include sibling funds).

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