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

Annotations declare destructive=true and idempotent=true, and the description adds substantial context beyond them: status transitions, job.closed events, bidders_notified, closed_at, the already_closed no-op, and the subtle expired-but-still-open row behavior. The only thing not covered is auth mechanics beyond 'needs your API key', but overall this is rich disclosure.

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?

A single dense paragraph with the core action front-loaded. Every clause carries information (events, counters, edge cases), though the em-dash-heavy packing makes it slightly harder to scan than a structured list would.

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, so the description carries the return-value burden and does so completely: bidders_notified, closed_at, and already_closed are all explained. Edge cases (expired jobs, still-payable bids) are covered, leaving nothing an agent needs 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?

Schema coverage is 67% and the schema already documents both reason and idempotency_key well. The description adds the mapping between reason values and the resulting status (filled vs closed, cancelled as default), which is meaningful semantics beyond the enum labels. job_id's meaning is self-evident.

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 and resource ('Stop taking bids on a job you posted') and immediately scopes it to the poster via API key. Distinguishable from siblings like postJob, myJobs, and claimListing without opening any schema.

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 tells the agent when NOT to use it ('Paying a bid fills the job on its own, so you only need this to close early or to cancel') and names the alternative path. Poster-only and key requirement are stated up front.

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