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

Fully discloses the side effects: moves job to in_progress, charges full bid into escrow, requires payment method and Stripe Connect account, validation checks. Annotations only give destructiveHint=true; the description goes far beyond by explaining the exact charge flow and prerequisites. No contradiction.

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?

Three sentences, densely packed with purpose, role restrictions, and side effects, all front-loaded. No filler. Every clause carries meaningful information.

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 there is no output schema, the description explains the outcome (job moves to in_progress, escrow charge) well enough. It covers authorization, prerequisites, and state change. Slight deduction for not stating whether the bid amount is returned if the job later is cancelled or fails, but that's beyond the core call, so still strong.

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 already covers 100% of parameters with a clear description ('The bid's UUID (not the job's)'). The description reinforces the meaning by explaining the tool's role relative to the bid, but adds no new parameter-specific detail beyond schema. Baseline 3, raised to 4 because the 'not the job's' caveat prevents a likely mistake, and the tool description aids semantic understanding.

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?

States a specific verb+resource: 'Accept a specific bid on a job, as that job's poster.' It clearly distinguishes from siblings like submit_bid, withdraw_bid, and get_bids by focusing on the acceptance action. It is unambiguous about who can act and on what.

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 explains when it applies ('as that job's poster'), what is rejected (bidder accepting their own bid, non-poster), and the conditions (saved payment method, bidder's completed Stripe Connect account). It also references a timing consideration relative to submit_bid, giving clear selection guidance.

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