search_symbol

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

With no annotations, the description carries full burden. It discloses normalization of Persian/Arabic characters and digits, and specifies the return format. While it doesn't cover error cases or rate limits, the disclosed behaviors are relevant and helpful.

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?

Three sentences, each with a distinct role: purpose, normalization detail, usage guidance and output format. No redundant words, front-loaded with the core action.

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 resolution tool with 2 parameters and no output schema, the description covers input, behavior, output format, and usage order. The return structure is explicitly stated, and sibling list provides context for tool ecosystem.

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 description adds meaning to the 'query' parameter by indicating it accepts symbol names and Persian text. However, the 'limit' parameter is not explained, and schema coverage is 0%, so the description only partially compensates.

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 resolves a Tehran-exchange symbol to its instrument code (insCode), which is a specific verb+resource. It also mentions Persian text normalization, distinguishing it from siblings like 'get_quote' or 'get_price_history' which require an insCode.

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?

Explicitly says 'Use this first when you only know the symbol name,' providing clear when-to-use context. It doesn't explicitly list when not to use, but the phrase implies it's a starting step, and sibling tools are for later stages.

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