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

No annotations are provided, so the description carries the burden: it does disclose 'Read only' and explains the returned shape (role, status values open/asked/yes given/ready, and claimant type PLAYER/AGENT/HOUSE). It omits auth/wallet requirements, ordering, and pagination, leaving real behavioral gaps for an unannotated tool.

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?

It is front-loaded with 'Seat board' but packed into one long run-on sentence with parenthetical game lists and status enumerations, which makes it denser than necessary. It earns most of its content but could be split for readability.

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?

With no output schema and three optional params, the description does the work of explaining what a caller gets back — per-seat role, status against the chain, and claimant identity — which is the key missing piece. Only auth/leader-wallet behavior is left to the schema's wallet description.

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%, so the schema already documents id, game, and wallet. The description adds minor value by mapping the game concept to named games (vehicle heist, convoy hit, Ledger job, apartment raid, Night Run), but adds nothing about the wallet parameter or the id filter beyond the schema.

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 states the resource clearly — a seat board of open crew requests across the five team games — and enumerates what each seat carries (role, status, claimant). It also names the sibling it defers to ('Claim one with claim_seat'), so an agent can distinguish the read board from the claim action, though the verb itself is only implied by 'Seat board'.

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 (browse open seats for team games) and names the follow-up alternative explicitly: claim_seat to take a seat. It doesn't spell out when-not-to-use or prerequisites, but for a read-only listing the routing is sufficient.

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