cancelAllRfqs

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

The description discloses side effects (inquirer vs. quoter cancellation consequences), rate limit (50 requests/second), and response format (array of results). No annotations are provided, but this description fully covers behavioral traits.

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 with clear sections (purpose, effects, rate limit, hint). Each sentence adds value. Could be slightly more structured, but overall efficient and front-loaded.

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?

For a tool with no parameters and no output schema, the description covers all essential aspects: purpose, side effects, rate limit, response shape (array of results), and no request body. No gaps detected.

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?

Since the tool has zero parameters, schema coverage is effectively 100%. The description adds no parameter-specific information, but baseline for 0 params is 4. It does provide context about rate limits and side effects, which are not parameter-related.

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 'Cancel all active RFQs for the authenticated account,' specifying the verb (cancel) and resource (active RFQs). It distinguishes from sibling tools like cancelRfq (singular) and cancelAllOrders by focusing on RFQs.

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 agent hint clarifies when to use the tool (cancel all active RFQs at once) and that no request body is needed. However, it lacks explicit guidance on when not to use it (e.g., canceling specific RFQs) and does not directly contrast with the sibling cancelRfq.

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