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

With no annotations, the description carries the full burden and does substantial work: it discloses header-only auth and where to obtain the token, plus a gating credential (human_verified, interim, with production intent noted). It stops short of saying what happens on failure, whether escrow holds are reversible, or what is returned.

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?

Dense but front-loaded: the core action leads, auth and credential constraints follow, and the vertical-dependent fields close. The parenthetical about signup/login endpoints is the only portion that could be trimmed.

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 an 8-parameter mutation tool with zero schema descriptions, no annotations, and no output schema, the description covers auth and the credential gate but leaves idempotency semantics and any indication of the return value (e.g., a booking/escrow identifier) undocumented.

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 0% across 8 parameters, so the description must compensate and only partly does. It usefully maps role fields to verticals (attendee / buyer+quantity / client / worker) and explains human_verified, but listing_id and especially idempotency_key are left unexplained.

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: book (or apply+pay for jobs) a listing into escrow. The escrow framing distinguishes it from a plain create, but the description never contrasts it with the sibling everlist_booking, so an agent must infer the split.

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?

Prerequisites are stated clearly (hub token in X-Hub-Token, human_verified must be true), which is more than most tools give. However, there is no explicit when-to-use-versus-alternative guidance, and the existence of a sibling named everlist_booking makes the omission material.

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