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

Annotations already declare readOnlyHint=true, so 'Read-only' is largely redundant. The description does add genuine behavior beyond annotations: a hard cap of 10 results and the fact that the response contains an app link into the stock universe where each company opens its full analysis. It stops short of covering rate limits, empty-result behavior, or ranking of matches.

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, front-loaded with the core action, followed by the result shape and the safety note. Nothing is padded and each sentence carries distinct information.

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?

With no output schema, the description partially compensates by describing the return (app link, up to 10 results). For a one-parameter read-only lookup that is nearly sufficient, though match ordering and no-result handling remain unstated.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains 'q' as a company name or ticker fragment. The description restates the same semantics ('by company name or partial symbol') without adding case-sensitivity, partial-match behavior, or whether spaces are acceptable. Baseline 3 applies 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?

States a specific verb and resource ('Find tickers') plus the input modality ('by company name or partial symbol') and a result cap ('up to 10 results'). An agent can distinguish this from siblings like screen_stocks or get_stock_score without opening the schema, since those are filtering/scoring tools rather than lookup tools.

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: use it when you have a name or symbol fragment and need a ticker. But there is no explicit when-to-use versus when-not, no mention of alternatives such as screen_stocks for broader filtering, and no note on what to do if no match is found. 'Read-only' is the only directive signal.

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