cancel_rfp

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

With no annotations at all, the description carries full behavioral burden for a destructive mutation. It discloses the zero cost ('[Free / $0.0000 USDC]') but never says whether cancellation is reversible, what happens to pending bids, whether escrowed funds are refunded, or what authorization is required beyond being the buyer.

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 core action and cost are front-loaded and the Args block is compact. The Keywords line and the 'cleanly terminate unfilled or expired requests' sentence partially restate the opening sentence, costing some tokens without adding much.

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 two-parameter mutation with no annotations and no output schema, the description covers the what, the rough when, and both parameters, but leaves the agent without the consequences of the operation (refunds, bid invalidation, reversibility) that matter most before invoking a cancel action.

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%, so the description must compensate, and it does add real meaning: buyer_id is identified as an 'EVM wallet address of the RFP creator' (a type/identity detail absent from the schema), and rfp_id is scoped as the 'target RFP ID to cancel.' It stops short of format examples, but it clearly beats the bare 'Buyer Id'/'Rfp Id' titles.

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 states a specific verb and resource ('Cancels an open or expired RFP') plus the domain ('multi-agent reverse auction market'), which cleanly separates it from siblings like create_rfp_auction, submit_rfp_bid, accept_rfp_bid and get_rfp_status.

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?

'Allows buyer agents to cleanly terminate unfilled or expired requests' gives clear situational context for when to call it, and the buyer_id arg implies the creator is the authorized caller. It does not, however, state when not to use it or point to alternatives such as letting a bid be accepted instead.

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