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

With no annotations, the description carries the burden and usefully discloses that this is board-only, returns no transaction, and requires each joiner to submit their own on-chain confirmation. It does not cover authentication requirements, whether the request can be cancelled, or expiry behavior beyond the schema's 'hours' field.

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 front-loaded with the core action and contains mostly useful details about board-only behavior and the join workflow. It is slightly dense with parentheticals and repeats some schema-level parameter guidance, but no sentence is clearly wasted.

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 six-parameter mutation-style tool with no annotations and no output schema, the description covers purpose, board-only behavior, visibility through open_seats, and the joiner confirmation workflow. It leaves some secondary details to the schema, such as hours and already-seated counts, but is sufficient for correct invocation.

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 description coverage is 100%, so the schema already documents all six parameters, including 'have' and 'hours'. The description reinforces game, optional ref, and role-number seats, but adds little beyond what the schema already says, so the baseline 3 is appropriate.

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 uses a specific verb and resource: 'post an open crew request as the leader' on the 'Seat board'. It also scopes the action with 'board only' and points to the sibling tool open_seats for visibility, so an agent can distinguish it from related crew tools.

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 clear context for when this tool applies: it posts to the board, returns no transaction, and joiners must still sign their own yes on chain. It does not explicitly contrast with create_crew, join_crew, or claim_seat, so it lacks full alternative-routing guidance.

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