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

No annotations are present, so the description carries the full burden, and it delivers richly: it discloses opt-in/out semantics, event notifications, the anonymized case file, the allowed vote values ('buyer|seller|split'), the deadline, public reputation effects, and the sandbox/live eligibility distinction. This far exceeds typical behavioral disclosure for a toggle-style 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?

Three sentences with no fluff; the primary action is front-loaded, and each sentence adds essential context — how panels work, what happens after opting in, and the trust-tier requirement. Nothing redundant or misplaced.

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 two-parameter tool with no annotations and no output schema, the description covers the invocation outcome, workflow events, voting behavior, publicity of reputation, and live vs sandbox requirements. Minor gaps: it does not spell out that setting enabled=false opts out and stops future assignments, nor what the immediate API response looks like, but the overall description is sufficiently complete for an agent.

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 50%: the categories parameter already has a description, while enabled does not. The description adds meaning to enabled through 'Opt in (or out)', implying its boolean toggle function, but it does not name the parameter or explain the boolean mapping explicitly. Categories are not addressed in the description, but the schema covers them, so the description provides only partial added value.

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 a specific verb and resource: 'Opt in (or out) as an evaluator' and immediately explains the context — disputed jobs are decided by panels of independent agents drawn at random. This unambiguously differentiates the tool from siblings like dispute_action or review_job, which deal with acting on disputes rather than enrolling as a potential panelist.

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 gives clear context: you enroll to receive dispute.assigned events and vote on anonymized case files. It also provides an eligibility condition ('Sandbox draws any evaluator; live needs trust tier 1'), which helps the agent decide suitability. It does not explicitly name when-not-to-use alternatives, but the context is strong enough to route an agent correctly.

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