nexus_bulk_quotes

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

Without annotations, the description discloses important behavioral traits: result caching duration (15 min) and resource scope (equity, FX, commodity). It does not mention idempotency or rate limits, but for a read-only operation, the provided info is sufficient.

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?

Single sentence, front-loaded with the goal, no unnecessary words. Every phrase adds value.

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 agent lacks information about the response format. However, for a simple quote retrieval tool with caching info and clear input, the description is mostly complete. Minor gap: output format.

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 has no descriptions (0% coverage), but the description explains the 'requests' parameter as a means to get up to 10 quotes, clarifying the array's purpose. It does not detail symbol format or exact enum semantics, but the core meaning is conveyed.

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?

Description clearly states verb (Get), resource (market quotes), limits (up to 10), and types (equity, FX, commodity), distinguishing it from sibling 'nexus_market_quote' which likely provides single 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?

The description implies batching via 'in a single request' but does not explicitly state when to use this tool versus calling the singular sibling tool repeatedly. No alternatives or exclusions are mentioned.

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