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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds useful semantic context about the ledger, escrow-upfront pot, and payout-on-goal/deadline behavior, but that describes the domain concept rather than the tool's own runtime behavior (pagination, freshness, error modes). It explicitly says no auth needed, which is a genuine behavioral detail.

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?

The description is dense and front-loads a long conceptual definition of hunting parties before stating the actual tool behavior, which sits near the end. Much of the enumeration (sign-ups, first runs, paid runs, etc.) is tangential to selecting and calling this list/read tool. It reads more like marketing copy than a tool contract.

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 read-only tool with one optional parameter and no output schema, the description adequately covers both modes of invocation and points to the downstream flow. It's not missing operational essentials, though it spends words on domain lore rather than report structure.

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 `party` parameter already has a description in the schema ('a party id or slug — omit for the board'). The prose restates this in narrative form without adding format or constraint detail beyond the schema. Baseline 3 applies.

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?

The description clearly states what a hunting party is (time-boxed pooled outcome bounty with a measured goal and USDC pot) and what the tool returns (board vs one party's progress). The verb 'list/read' is somewhat buried under conceptual framing, but the tool's function is discernible. It doesn't explicitly contrast itself with the many sibling party_* tools by name, though it does sequence them.

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?

It gives a clear usage rule: no arguments returns the board, passing `party` returns one party's detail. It also names the follow-on flow (party_join → party_link → party_progress / party_proof). It stops short of saying when NOT to use this in favor of a dedicated tool, but the argument-driven split is explicit and actionable.

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