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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds useful context about the scope (US stocks, options, indices, forex, crypto) and the exact fields returned. It does not disclose any potential quirks like pagination or rate limits, but given the strong annotations, the description provides additional value without contradicting the structured metadata. A score of 3 reflects that it adds some behavioral context beyond annotations but not deep detail.

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 long, with no redundant information. It front-loads the primary purpose and includes a clear action-oriented verb. Every sentence adds value, and it avoids unnecessary 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 has an output schema and strong annotations, but the description leaves parameter semantics entirely unaddressed. It covers the core function and return fields sufficiently for a basic use case, but for a tool with 8 parameters and zero schema descriptions, it lacks essential guidance on filtering, sorting, and limiting. The description is minimally adequate but not complete.

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 0%, meaning no parameter descriptions are provided in the schema, and the description does not compensate. The description mentions markets and returns but does not explain parameters like search, limit, market, exchange, or sort. With 8 parameters, the agent would have to rely solely on the schema's bare property names and examples. This is a significant gap that the description should have addressed.

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 that the tool searches a reference universe for tickers across multiple asset classes, and specifies the returned fields (symbol, name, market, etc.). It also gives a concrete use case: resolving a company name to a tradable symbol. This distinguishes it from siblings like ticker_details (which likely provide details for a specific symbol) and exchanges (which likely list exchanges).

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 provides a clear when-to-use scenario: 'Use to resolve a company name to a tradable symbol.' It implies the tool is appropriate for symbol lookup. However, it does not explicitly mention when not to use it or offer alternatives like ticker_details for when a symbol is already known, so it lacks explicit exclusions. This is still adequate context but not exhaustive.

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