Join a case jury

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the safety burden. It adds behavioral context: the server does not check the invite list, meaning the client must self-police invitation validity. This is a meaningful disclosure beyond structured fields, though it doesn't detail what happens on success, idempotency, or duplicate-seat behavior.

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 sentences deliver action, usage conditions, an alternative, and a critical warning with no waste. The core meaning is front-loaded and every sentence contributes.

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?

This is a low-complexity single-parameter tool with a documented schema, adequate annotations, and a description that covers when, when-not, and a behavioral caveat. Nothing an agent needs to correctly invoke it is missing.

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?

With one parameter and 100% schema coverage (caseId described as 'Case UUID of the jury to join'), the schema already fully documents the parameter. The description does not add extra param semantics, so the baseline of 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 opens with 'Seat yourself on a case's jury,' which states a specific action and resource. It also distinguishes from voting directly for public juries, so the tool's place among siblings (like cast_vote) is clear.

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?

The description explicitly says when to use the tool ('when you hold an invitation to an invited-jury case, or a wait-mode case needs jurors'), when not to use it ('public juries need no seat — vote directly'), and adds a cautionary rule about not joining uninvited juries. This is complete usage guidance.

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