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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It implies a read-only search but does not explicitly state this, nor does it mention rate limits, response format, pagination, or any side effects. This is a significant gap given zero annotation support.

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 two sentences, concise, and front-loaded with the main action. Every sentence adds relevant information about purpose and use case without unnecessary verbosity.

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 simple search tool with three parameters and no output schema, the description is fairly complete. It explains the tool's value proposition and even hints at the output (ticker symbols, company names, exchange details). However, it could benefit from a brief note on the default limit or exchange filter behavior to fully compensate for the lack of annotations and output schema.

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%, so the input schema already documents all three parameters. The description adds slight context by mentioning 'full or partial company or asset name' for the query, but it does not meaningfully enhance the schema's parameter descriptions for limit or exchange.

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's purpose: searching for ticker symbols, company names, and exchange details for equities and ETFs. It provides a specific use case (retrieving ticker symbols from a known company name) but does not explicitly distinguish itself from sibling tools like searchCompaniesByName or searchSymbol.

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 gives clear context on when to use the tool: 'when you know the full or partial company or asset name but not the symbol identifier.' It does not, however, mention when not to use it or describe alternatives, stopping short of a full 5.

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