get_prices

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

Without annotations, the description carries the full burden of behavioral disclosure. It reveals a key behavior: unresolved symbols are reported in 'failed' rather than failing the whole call, which is valuable for agents. It does not mention rate limits or data freshness, but the disclosed partial-failure behavior is significant.

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 concise and well-organized: a one-sentence purpose, followed by clear parameter definitions, and a note on failure behavior. No redundant or vague wording.

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 tool's moderate complexity and the presence of an output schema, the description covers essential aspects: batch pricing, market scope, and partial failure handling. It does not detail return fields, but the output schema covers that. It is sufficiently complete for a read-only price tool.

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 0% description coverage, so the description must compensate. It explains 'symbols' as up to 50 tickers and clarifies that 'market' can be 'crypto', 'stock', or 'idx' and applies uniformly. This adds meaning not in the schema, though exact ticker formats are not specified.

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 'Get current prices for several instruments at once' with a specific verb and resource, and the 'at once' phrase distinguishes it from the sibling tool 'get_price' which likely handles single instruments. It also specifies market types, further clarifying its scope.

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 clear context for when to use this tool: when you need current prices for multiple instruments concurrently. It does not explicitly exclude alternatives like 'get_price' for single instruments, and there are no when-not-to-use statements, but the batch context is evident.

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