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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description meaningfully adds the data source ('Yahoo Finance via yfinance'), that no API key is required, and the shape of the return (symbols with exchange and asset type). It does not discuss rate limits or result ordering, but the added context is genuinely useful.

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?

Core purpose and usage guidance are front-loaded, followed by a scannable bullet list and a source note. The bullet list is slightly redundant with the leading sentence but each line adds routing value; no significant 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?

An output schema exists, so return values needn't be explained, and annotations cover the safety profile. Purpose, usage, and the key query/asset_type semantics are present, making it complete enough for a read-only lookup tool; the unexplained boilerplate parameters are the only gap.

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?

The description restates the asset_type options and implies the query semantics, but this largely duplicates what the schema's $defs already document for query, asset_type, and max_results. It adds nothing about the many boilerplate parameters in the schema (wholesaler_ids, source_resource_id, mcp_prompt_id, etc.) that appear irrelevant to a ticker lookup, so the description does not compensate for the reported low top-level coverage.

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 verb and resource: 'Search for a Yahoo Finance ticker symbol by company name, fund name, or keyword.' An agent can immediately tell what it produces (matching symbols with exchange and asset type). It does not explicitly name or distinguish itself from close siblings such as GetTickerInfo, MapInstrumentIds, or SearchFigiInstruments, so it stops short of a 5.

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?

It gives an explicit 'Use this tool when' block with three concrete scenarios (name-but-not-symbol, ETF/mutual fund lookup, disambiguating similarly named securities), which is clear routing guidance. It stops short of naming alternatives (e.g., when to use GetTickerInfo instead) or giving explicit when-not conditions.

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