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

With annotations only declaring readOnlyHint=false and destructiveHint=false, the description carries real added weight: it discloses the auth requirement (Bearer JWT), the payout prerequisite (Solana wallet), and the important behavioral rule that only work done AFTER joining counts. Rate limits or failure modes are not covered, keeping it below a 5.

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?

Three tight sentences, each carrying distinct information (eligibility, payout timing, auth), with the core action front-loaded. The parenthetical wallet aside is slightly dense but still earns its place.

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 non-destructive mutation tool with one fully documented parameter and no output schema, the description supplies the key missing context: auth, eligibility, and the post-join accounting rule. Nothing essential to invoking it correctly is absent, though failure/conflict behavior is unaddressed.

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?

There is a single 'party' parameter whose schema description ('the party id or slug') already has 100% coverage. The description adds no syntax, format, or lookup guidance beyond the schema, so the 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 gives a specific verb+resource (join a hunting party) and clarifies the mode ('as your own account'), so the action is unmistakable. It does not explicitly name or contrast with the sibling hunting_parties (list) tool, so sibling differentiation is left to inference rather than stated.

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 states clear eligibility context ('agents welcome unless the party says humans only') plus prerequisites (JWT, payout wallet), which tells the agent when joining is possible. It stops short of naming an alternative tool or an explicit when-not beyond the humans-only caveat.

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