price_bysymbol_symbol

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

With no annotations, the description carries the transparency burden. It states the tool returns USD prices and supports up to 100 symbols, but does not disclose whether prices are current or historical, the response format, or any rate limits. Adequate but lacks depth.

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 sentence that front-loads the key action and resource. Every word earns its place, with no wasted space.

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 no output schema, the description should explain what the tool returns. It says 'Get USD prices' but does not specify if these are current prices, the data format, or any additional metadata. For a simple price tool, this is adequate but not fully 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?

The parameter 'symbol' is already described in the schema (100% coverage). The description adds value by specifying the comma-separated format and the maximum of 100 symbols, which is not in the schema description.

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 'Get', the resource 'USD prices', and the method of specifying symbols (comma-separated). This distinguishes it from sibling tools that focus on historical data, technical analysis, or other assets.

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 mentions support for up to 100 comma-separated symbols, which guides when to use this tool (multiple current prices). However, it does not explicitly state when not to use it or mention alternative tools for historical or single-symbol queries.

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