searchSymbol

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety and repeatability profile is covered without help from the text. The description adds mild context by noting the search spans multiple global markets and can match on either company name or symbol. It does not disclose result size behavior, pagination interaction with the limit parameter, or what a hit looks like, which would have been valuable additions beyond the annotations.

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?

Two short sentences with the core capability front-loaded, which is efficient for a simple search tool. The opening word 'Easily' and the API product name are marketing filler that earn no place, keeping it short of perfect. Structure is otherwise clean with no redundancy.

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 three-parameter read-only search tool with full schema coverage and no output schema, the description need not explain return values in detail. Still, an agent lacks any sense of whether results are a ranked list of symbol/name pairs or whether the limit cap applies per exchange, and the absence of sibling differentiation leaves the definition only minimally adequate. It is complete enough to invoke but not complete enough to invoke confidently among many near-neighbors.

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 description coverage is 100%, so the query, limit, and exchange parameters are already documented in the input schema, which sets the baseline at 3. The description reinforces that queries may be either a company name or a symbol, a useful clarification about the query field. It says nothing about the exchange filter or the default of 50 results, so no meaning is added beyond the schema.

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 the ticker symbol of a stock by searching company name or symbol across global markets. That is clear enough to understand the operation at a glance. However, it does not distinguish itself from several close siblings such as searchCompaniesBySymbol, searchName, or getCompanySymbols, so an agent cannot tell from the text alone which one to reach for.

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 how to use it (pass a company name or a symbol) but gives no explicit guidance on when to choose it over alternatives. With a crowded family of symbol/name lookup tools in the sibling list, the absence of any routing or exclusion statement is a real gap. There is no mention of prerequisites, markets covered in concrete terms, or what to do when no match is found.

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