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

Annotations already declare the operation read-only, idempotent, and non-destructive, so the description is not burdened with safety disclosure. It adds useful behavioral context by saying results include the exchange and that unverified listings are explicitly marked unchecked, which is a meaningful caveat for an agent choosing whether to trust a result.

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 two sentences with no wasted words: the first leads with the verb and resource and packs in search scope and output, the second adds the one important caveat. It is front-loaded and easy to scan.

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 simple search tool, the description covers query types, returns (ticker and exchange), and the unchecked-listing caveat; the output schema and read-only annotations fill the rest. No critical detail such as pagination or special permissions seems needed to call this correctly.

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?

With 100% schema coverage, the baseline is 3, but the description adds a real semantic nuance: it says query can be a ticker fragment, not just an exact ticker as the schema might suggest. It does not add anything about the base parameter, but the schema already documents it fully.

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 resource (the ticker for a fund or company) and the three query types (name, ticker fragment, ISIN), and states the exchange is included in results. It is specific enough to be distinguished from the portfolio-focused siblings, though it does not explicitly contrast itself with validate_symbols.

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 intended call context is implied: use this tool when you need to resolve a fund/company name, ticker fragment, or ISIN into a ticker and its exchange. There is no explicit statement about when to prefer an alternative such as validate_symbols, nor any exclusions or prerequisites.

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