cancelRfq

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

Discloses rate limit (50 req/s), parameter priority, and side effect (quotes become invalid). Without annotations, these are essential. No mention of idempotency or error cases, but sufficient for the tool's simplicity.

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 clear and front-loaded with purpose, then parameter rule, side effect, rate limit. Slight redundancy in the agent hint repeating earlier content, but overall concise.

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, parameter usage, side effect, and rate limit. Lacks error handling or response format, but acceptable for a simple cancel operation. Distinguishes sufficiently from siblings.

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 coverage, description compensates by explaining the parameter choice, priority rule, and that one must be provided. Adds meaning beyond the schema's empty descriptions.

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?

Description clearly states 'Cancel an active RFQ' with specific verb and resource. It details parameter behavior (rfqId vs rfqLinkId) and side effect (invalidates quotes), distinguishing it from siblings like cancelAllRfqs and cancelQuote.

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 parameter usage guidance ('You must pass either rfqId or rfqLinkId') and effect on quotes. Does not explicitly compare to cancelAllRfqs, but the context is clear. Implicit guidance is adequate.

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