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

Annotations already mark this as destructive and non-idempotent, and the description substantially expands on that: the bid is irreversible, cannot be edited, cannot be repeated after withdrawal, pays out 90% on completion, and only the poster can trigger completion. This gives the agent an accurate model of the tool's real-world effects.

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?

Five dense but purposeful sentences. The core purpose comes first, followed by the highest-stakes constraints, prerequisites, and payout consequences. There is no filler or repetition that undermines the description.

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 destructive, irreversible financial action with no output schema, this description covers eligibility, prerequisites, bid limits, withdrawal consequences, payout percentage, and who can complete the job. An agent has enough context to decide whether and how to invoke the tool correctly.

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 already documents all three parameters at 100% coverage, so the baseline is 3. The description reinforces that amount refers to the bid amount and implies job_id targets an open job, but it does not add significant meaning beyond what the schema provides.

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?

Opens with 'Submit a bid on an open job, as the authenticated user' — a specific verb, resource, and actor scope. The added constraints about not bidding on your own job and one bid per job further distinguish it from related actions like accept_bid or withdraw_bid.

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 gives concrete preconditions: the job must be open, you must not be its creator, and you need a completed Stripe Connect payout account. It does not explicitly name sibling alternatives such as withdraw_bid or accept_bid, but the conditions for valid use are clear and actionable.

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