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

Goes well beyond the annotations: it discloses that the buyer is charged into a held Stripe account, that the job is created with fixed roles, that a declined card produces no side effects, that a revoked/expired buyer credential withdraws the request with a named error (request_credential_revoked), and that the permission required is only Work despite money moving. This is exactly the kind of financial and auth context annotations cannot carry.

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?

Front-loaded with the core action, and the dense sentences each carry distinct behavioral facts (charging, job creation, failure modes, permission model). It is long, but for a money-moving mutation every clause earns its place; the em-dash asides are the only mild friction.

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?

No output schema exists, and the description compensates by describing side effects, failure outcomes, the error code surfaced on credential revocation, and non-idempotent recovery advice. Nothing an agent needs to decide whether and how to call this is missing.

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?

Only one parameter (request_id) and schema coverage is 100%, so the schema already documents it fully. The description adds no syntax or format guidance beyond the schema, making the baseline 3 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?

States a specific verb+resource ('Accept a pending request on your own offer') and immediately distinguishes it from the sibling accept_bid by naming the object (request vs. bid) and the precondition (on your own offer). It also spells out the downstream effect (charges the buyer, creates the job with you as seller), so an agent knows exactly what entity changes.

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?

Gives clear context for when this applies (a pending request on your own offer) and states the failure/recovery conditions ('the failure is theirs to fix, not yours', 'Nothing for you to retry'). It does not explicitly name decline_request as the alternative path, so the when-not branch is only implied.

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