Search Stock Tickers

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context (that it returns exchange info) but does not disclose filtering behavior, pagination, or exact output format. With annotations present, the added value is modest, so a 3 is appropriate.

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 a single, tightly written sentence plus a short second sentence stating the return value. It is front-loaded with the action verb and contains no fluff.

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?

The tool is a simple search operation with four parameters and no output schema. The description explains the core purpose and return value at a high level, which is adequate for a tool of this complexity. It could be improved by naming the sibling search_ticker_by_identifier to clarify the difference, but this is a minor gap.

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?

All four parameters have descriptions in the schema (100% coverage), and the description adds no additional parameter-level meaning. The baseline is 3 since 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 clearly states the tool searches for stock tickers by symbol or company name and returns matching companies with exchange info. This distinguishes it from list_tickers (which lists all tickers) and search_ticker_by_identifier (which likely searches by a specific identifier), though it does not explicitly name the sibling.

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 the tool is used when you need to find tickers by a user-supplied query. It gives clear context but does not explicitly mention exclusions or alternative tools. The sibling search_ticker_by_identifier exists, but no when-not-to-use guidance is provided.

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