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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which fully establishes the safe read-only nature. The description adds that results are for 'security identification' — a forward-looking context suggesting this is a lookup/precursor step. With comprehensive annotations in place, the description's additional behavioral context is reasonable and non-contradictory.

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, compact sentence that states purpose, input modality, and intent with zero filler. Every word earns its place, and the sentence is front-loaded with the primary action verb. Among the evaluated examples, this is near-optimal conciseness.

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 read-only search tool with 100% schema coverage, full annotations, and an output schema present, the description is sufficiently complete. The agent can safely invoke it knowing it is non-destructive and idempotent, and can parse results via the output schema. The only minor gap is lack of explicit guidance on how results are ordered or what happens with an unmatched query, but the annotations and schema carry the burden well.

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%: both 'query' (a company name or ticker fragment) and 'limit' (max results) have descriptions in the schema. The description usefully frames the primary parameter as enabling search by either ticker text or company name, confirming it accepts fuzzy/incomplete input. It adds value by clarifying the semantic flexibility of 'query' beyond the schema's minimal wording.

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 uses a specific verb ('Find') plus a clear resource and scope ('ticker symbols by company name or ticker text for security identification'). It clearly distinguishes this search-type tool from sibling market tools like market_quote, market_company_profile, and market_price_history, which retrieve specific data rather than resolving identifiers. The word 'search' in the name is fully expanded with the what/how/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?

The description implies usage context ('for security identification') indicating this resolves names to tickers, which is a prerequisite step before querying quote/profile/price tools. However, it does not explicitly state when NOT to use it or name alternative tools. Given the large sibling set, the guidance is adequate but falls short of explicit exclusions or alternative pointers.

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