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

Annotations already declare readOnlyHint=true, and the description restates 'Read-only' consistently rather than contradicting it. Beyond annotations it adds genuinely useful behavior: a hard cap of up to 10 results and the fact that the response carries an app link to the stock universe where each company opens its full analysis. It stops short of describing match ranking or empty-result behavior.

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?

Three short sentences, each carrying new information: what it matches, the result limit, and what the response contains. The core capability is front-loaded with no filler or repetition.

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 lookup with no output schema, the description covers purpose, result limit, and response payload shape, which is enough for correct invocation. Minor gaps remain around result ordering and zero-match handling, but 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?

Schema coverage is 100% and the single parameter q is already documented as 'a company name or ticker fragment.' The description's phrase 'company name or partial symbol' largely mirrors the schema, adding only the clarification that partial symbol fragments are accepted. Baseline 3 is appropriate 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?

The description states a specific verb and resource: 'Find tickers by company name or partial symbol.' An agent immediately understands the lookup semantics. It does not, however, distinguish this from sibling lookup tools such as resolve_company or screen_companies, so sibling differentiation is absent.

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?

Usage is implied by 'by company name or partial symbol' and by the 10-result cap, which signals this is a discovery/autocomplete step. There is no explicit when-to-use versus resolve_company or screen_stocks, and no guidance on what to do when the query returns nothing or when more than 10 matches exist.

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