acceptNonLpQuote

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals the rate limit (50 req/s) and caller restriction (RFQ creator). However, it does not describe side effects, reversibility, or state changes the RFQ undergoes, which are important for an 'accept' operation. Adequate but has gaps.

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: a clear main sentence, a clarifying sentence, a rate limit, and a structured agent hint. Every sentence adds value without redundancy. Well-organized for quick comprehension.

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 the tool has only one parameter and no output schema, the description lacks information about the return value or success criteria. It implies the action is taken but doesn't confirm what happens after calling. May be sufficient for a simple toggle, but missing outcome details.

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 description coverage is 0%, so the description must compensate. It adds that 'rfqId' is the ID of the target RFQ, which is helpful but minimal. No format, source, or example is provided. For a single required parameter, this is adequate but not excellent.

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 enables acceptance of non-LP quotes for a specific RFQ, distinguishing it from other quote-related sibling tools like applyQuote, createQuote, or confirmQuote. The verb 'accept' and resource 'non-LP quotes for a specific RFQ' are specific and unambiguous.

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 explicitly says to use this endpoint to allow non-LP counterparties to quote on your RFQ, and notes that only the RFQ creator can call it. This provides clear use context and an important precondition. It does not list explicit alternatives or when not to use, but the hint is sufficient for its purpose.

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