lookup_symbols

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

Annotations already declare safe read (readOnlyHint, idempotentHint). Description adds that query can be company name, ticker symbol, or partial match, providing useful behavioral detail without contradicting 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 sentences, front-loaded with main action, efficient and no redundant words.

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?

Simple tool with 2 parameters and an output schema; description fully covers the search behavior and optionality without over-explaining.

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 already describes both parameters. Description restates the schema's purpose without adding new semantic depth, earning baseline score for high schema coverage.

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?

Clearly states the verb 'Search' and the resource 'symbols' using a query string. Elaborates on scope (stocks, ETFs, assets, optionally indices) and distinguishes from sibling tools like get_symbol_data which retrieves details for a known symbol.

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?

Implied usage: use when you have a text query to search for financial symbols. Mentions optional include_indices but no explicit exclusion guidance or comparison with alternatives like get_symbol_data.

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