getQuotesRealtime

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

Despite no annotations, the description fully discloses behavioral traits: returns non-final quotes sorted descending, rate limit of 50 req/s, potential latency during volatility, and detailed parameter priority rules.

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 mostly concise but slightly repetitive (priority order appears twice). However, it is well-structured with clear sections and front-loaded key information. Could be tightened by removing redundancy.

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 or annotations, the description covers purpose, behavior, limitations, rate limit, and usage hints. It lacks details on what happens when no parameters are provided (e.g., returns all non-final quotes) and pagination, but it is adequate for a real-time query 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?

With 0% schema description coverage, the description adds some meaning through priority order and the quoteLinkId condition, but it does not explain the purpose of each parameter (e.g., rfqId, quoteId, traderType). The agent must infer that these are filters, but more explicit semantics would be beneficial.

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 real-time quotes from the RFQ engine, returning non-final quotes sorted by createdAt. It distinguishes itself from the historical Get Quotes tool, as noted in the agent hint.

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?

Explicit guidance is provided: use for real-time data, for historical use Get Quotes. Priority order and condition on quoteLinkId are explained, helping the agent decide when to use this tool and which parameters to prioritize.

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