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

Beyond the readOnlyHint=true annotation, the description discloses meaningful behavioral traits: data is 'settled' (not live/intraday), SEC assets come from filings, dividend history is 'currently primary-listing-only,' and issuer-trained short-interest forecasts/squeeze scores are excluded from ETF analytics. These caveats tell the agent what the tool will and will not return, all consistent with the readOnly and closed-world annotations.

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 core function is front-loaded in a concise first sentence, followed by logically ordered sections: same-ticker routing, holdings differentiation, filing caveat, data limitations. However, the routing catalog is long and reads like a data directory, and the final clause about 'issuer-trained short-interest forecasts and squeeze scores' is cryptic — informative but not zero-waste.

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 one-parameter read-only tool with no output schema, the description covers what is returned (settled performance, SEC assets, allocation, top holdings), what alternative tools handle other data categories, and known limitations. Minor gaps remain: no return format or units for SEC assets/allocation, and no indication of performance time periods.

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 coverage is 100%, and the schema already documents the single parameter well: 'Exact exchange-traded ticker (for example SPY, VOO, or IVV).' The description only reinforces exact ticker matching ('For this same exact ETF ticker') without adding new parameter semantics, so the baseline 3 applies.

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 opening sentence names a specific verb ('Get'), a specific resource ('ETF profile'), and the exact deliverables: 'settled performance, SEC assets, allocation and top holdings.' It immediately differentiates from the most confusable sibling, GetEtfHoldings ('instead returns investments inside the ETF'), so an agent can distinguish them without opening schemas.

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 goes beyond vague context by enumerating explicit routing rules: prices → GetStockPrices/GetLatestClosingPrices, intraday quotes → GetLiveQuote, options → GetOptionExpirations/GetOptionChain/GetOptionContract, short interest → GetShortInterest, and so on. It also states when-not-to-use: ListFilings/SearchDocuments 'may include sibling funds, not just this ETF series,' which is exactly the guidance an agent needs to avoid scope errors.

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