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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the searchable scope (US stocks, ETFs, crypto pairs) and match key (name or ticker); it says nothing about result ordering, ranking, or whether the limit truncates silently.

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?

A single front-loaded sentence with no filler; the purpose and output intent arrive in the first clause and nothing is wasted.

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 read-only lookup with three fully documented parameters and complete annotations, the description is nearly sufficient. It leaves the exact return shape (symbol/name pairing) and limit-truncation behavior unstated, a minor gap given there is no output schema.

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%, with the enum and limit bounds fully documented in the schema, so the baseline is 3. The description's 'name or ticker' and asset-type phrasing mirrors the schema without adding meaning beyond it.

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 gives a specific verb+resource: 'Find the symbol' across 'US stocks, ETFs and crypto pairs' matched by 'name or ticker'. This clearly distinguishes it from the quote/indicator siblings, which consume symbols rather than resolve them, so an agent knows exactly what this tool returns and why.

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?

'Find the symbol to use' implies the tool is a lookup step that feeds downstream quote tools, but the description never states when to call it versus alternatives or any exclusion. Usage is inferable rather than stated, which fits the 'implied usage' level.

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