createRfq

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

Discloses rate limit (50 req/s) and constraint that all legs share same base/settlement coins. With no annotations, description carries burden; missing details on authorization, idempotency, or side effects.

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?

Well-structured with bullet points and bold labels. Every sentence adds value; no redundancy. Front-loaded with purpose.

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?

Covers purpose, prerequisite, rate limit, and leg structure, but missing explanation for three optional parameters (rfqLinkId, anonymous, strategyType) and no return value/error info.

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%, but description explains leg structure (category, symbol, side, qty). Does not cover rfqLinkId, anonymous, strategyType, leaving gaps for those parameters.

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 the tool creates a new RFQ to solicit pricing from selected counterparties, specifying the verb, resource, and purpose. It distinguishes from siblings like cancelRfq and getRfqs.

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?

Explicitly mentions prerequisite call to Get RFQ Config and provides agent hint with step-by-step guidance. Lacks negative usage conditions but provides clear context.

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