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

Annotations only say write-but-not-destructive; the description adds substantial behavioral context: the settle-flips-first ordering, payout by attributed share, firing party.settled, returning final progress, and the auth requirement (Bearer JWT). Money-safety rules (escrow solvency, claim-before-send, skipping blocked accounts and wallet-less members) further disclose side effects and failure modes beyond the annotations.

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 definition is a dense wall of prose whose first two-thirds describes the HUNTING PARTY concept (presets, pots, targets, attribution) rather than this operation, and it points to a full reference URL that makes the inline exposition redundant. The actionable content is back-loaded instead of front-loaded, so sentences do not all earn their place in a tool definition.

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 money-moving tool with no output schema, the description is fairly complete: it covers caller eligibility, automatic settlement, the payout path, auth requirement, skip conditions, and the return (final progress). It is verbose rather than gap-ridden.

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?

Single required parameter with 100% schema coverage, which sets the baseline at 3. The description never mentions the `party` argument itself, so it adds no meaning beyond the schema's "the party id or slug".

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 tool-specific sentence ("SETTLE NOW… flips live → settling before any payout row, pays by attributed share, fires party.settled") states a precise verb+resource and the mutation it performs. However, it is buried beneath two-thirds of HUNTING PARTY domain exposition, and it never names siblings like party_progress or party_join to differentiate scope.

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 explicitly states who may invoke it ("the creator or the House") and that the 2-minute ticker settles automatically on goal met / deadline, which tells the agent this call is often unnecessary. It does not name an alternative for checking progress, but the automatic-settlement context is clear usage guidance.

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