getQuotes

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

No annotations provided, but description fully discloses behavioral traits: not real-time, sorted by createdAt descending, supports cursor-based pagination, rate limit 50 req/s, priority logic, and parameter invalidity. This adds necessary context for agent decision-making.

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?

Description is concise, uses bullet points and bold for emphasis, and front-loads the main purpose. It is well-structured with separate sections. Minor extra wording like 'Agent hint' slightly reduces conciseness but adds clarity.

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 and 7 parameters, description covers filtering, pagination, sorting, rate limit, and real-time distinction. However, it lacks details on the expected output format or fields returned, which is important for a query tool. Slightly incomplete for an agent to fully understand the return value.

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 coverage is 0%, so description must compensate. It mentions filtering by IDs, trader type, and status, and explains priority and invalidity. However, it does not describe limit, cursor, or the exact meaning of each parameter in detail. Some parameters like limit and cursor are only implied through pagination mention.

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 it queries historical quotes with filtering options, and explicitly contrasts with the real-time endpoint. The verb 'Query' and resource 'historical quotes' are specific, distinguishing it from sibling tools like getQuotesRealtime.

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?

Provides explicit guidance: when to use this tool (historical data) vs Get Quotes Realtime (live data). Also details priority among identifiers (quoteId > quoteLinkId > rfqId) and a constraint (quoteLinkId invalid with traderType 'request').

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