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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false), the description discloses critical side effects and preconditions: job state change to in_progress, charging the poster's full bid amount held in Stripe, requiring a saved payment method, and re-checking the bidder's Stripe Connect payout account. This gives an agent a solid basis for predicting the tool's impact.

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 three sentences, each conveying essential operational information: the action and scope, the authorization rule, and the financial/precondition details. There is no filler; the contextual note about re-checking Stripe Connect is defensible because time can pass between submit_bid and accept_bid.

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 financial mutation with no output schema, the description covers the action, state change, permissions, payment method requirement, and bidder payout account requirement. It does not mention what happens if the bid is no longer valid or the job is not in a biddable state, but those are edge cases beyond the tool's core contract.

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?

The input schema's description for bid_id already explains 'The bid's UUID (not the job's)', which semantically disambiguates the only parameter. The tool description refers to 'a specific bid' but does not add substantial new parameter meaning. Since schema coverage is 100%, the baseline of 3 is appropriate.

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 leads with a specific verb and resource: 'Accept a specific bid on a job, as that job's poster.' It states the core outcome, moves the job to in_progress, and clearly distinguishes this from bidder-side actions like submit_bid or withdraw_bid by restricting it to the poster.

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 description clearly indicates who should use this tool ('Only the job's poster can do this') and who should not ('the bidder accepting their own bid is rejected, as is anyone who isn't the poster'). It provides clear context but does not explicitly name alternative sibling tools, such as withdraw_bid, for the bidder case.

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