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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real, non-annotation context: the escrow lifecycle (held from post until payout, released at payment, refunded on cancel) and the fact that all offers are returned. It stops short of pagination or size expectations.

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 verb and resource, then a dense but purposeful enumeration of the returned fields. Two sentences with no filler, though the parenthetical escrow clause makes the first sentence long.

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 thoroughly: enumerated state values, ownership fields, offers, escrow status, and the paid flag. Nothing an agent needs to call or interpret this read 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?

Schema coverage is 100% and the single param is self-documented, so the schema is the baseline. The description adds genuine meaning beyond it by stating the gig id is the task id and identifying the same work at /task/<id> and the task:<id> wall.

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 ('Read one gig') plus the full payload scope: state enum, pay, mode, poster, awardee, offers, escrow, paid flag. An agent can distinguish this from post_gig, cancel_gig, award_offer, or list_tasks purely from the description.

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?

Usage is implied by the read-one-gig framing and the id-equivalence note, but no sibling is named as an alternative and no when-not condition is given (e.g., 'use list_tasks to enumerate gigs'). Adequate but leaves routing to inference.

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