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

Annotations only carry safety flags (destructiveHint=true, idempotentHint=false); the description goes well beyond them by naming the required verified email and Stripe Connect payout account, the one-active-offer limit, the immutable record, and the ended offer remaining public. That is exactly the operational context an agent needs before invoking a mutation.

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?

Purpose and the post_job contrast are front-loaded, and the prerequisites and invariants follow in a logical order. It is dense but nearly every clause carries a distinct constraint; the pricing sentence is the only one that could be trimmed slightly.

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 three-required-param creation tool with no output schema, the description covers purpose, prerequisites, mutation semantics, and account limits, leaving nothing an agent needs for a correct call unstated.

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 100%, so the baseline is 3, but the description adds real meaning: starting_price is advisory and not enforced, and the buyer names their own amount. The title-as-job-title linkage is also noted in the schema. It stops short of format guidance for title/description.

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 ('Post a standing offer: what you provide and the price to start from') and immediately distinguishes itself from the closest sibling ('Free, unlike posting a job'). An agent can identify the tool without opening the 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?

Names the alternative (post_job) and the condition that separates them, and routes edits to the end-and-repost flow instead of an update tool. Exclusions and constraints (one active offer, never editable) are stated explicitly.

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