asset_search

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

With no annotations, the description carries the full burden, but it only says 'Search Yahoo Finance' and does not disclose whether the operation is read-only, any rate limits, or the shape of results. It provides minimal behavioral insight beyond the search action.

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 concise sentence with no filler words, efficiently conveying the core action without 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?

Given the simple nature (two parameters, one required) and the existence of an output schema, the description is minimally adequate but lacks usage criteria, parameter details, and any behavioral disclaimers. It doesn't fully leverage the opportunity to guide tool selection or disclose constraints.

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?

The schema has no descriptions (0% coverage), and the description only indicates that the query matches symbols, asset types, and exchanges. It does not explain the 'limit' parameter or provide format/constraints for 'query', leaving the agent with incomplete information.

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 verb 'Search', the data source 'Yahoo Finance', and the output categories 'matching symbols, asset types, and exchanges', making its purpose immediately clear and distinct from sibling tools like validate_symbol or bulk_quotes.

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?

No guidance is provided on when to use this tool versus alternatives such as validate_symbol or bulk_quotes. It simply describes what it does without context for selection, exclusions, or prerequisites.

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