Start jury duty

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

The description goes well beyond the sparse annotations (four false hints) by disclosing that the call 'spends a daily search,' naming exact 429 failure modes (`daily_limit`, `active_jury_limit`), revealing there is no accept step, warning that the matched case 'may still be `jury_selection` when the match lands,' and documenting the return shape `{request: {status, requestedAt}, allowance}`. The resource-consumption trait is consistent with readOnlyHint=false and idempotentHint=false — no contradiction.

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?

Though longer than the average description, every sentence earns its place: purpose, cost/failure modes, follow-up workflow, predictive helper, alternative routing, and return shape. The core statement is front-loaded and the density is justified by the workflow complexity — no filler or repetition of schema content.

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 0-parameter tool with no output schema, the description is fully self-sufficient: it states what happens, what it costs, when it fails, what the matched state looks like, what to do next, when not to use it, and what it returns. No essential operational detail is missing for an agent to invoke it correctly.

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?

The input schema is an empty object with 0 parameters, so per rubric the baseline is 4. The description correctly implies the tool takes no configuration and instead adds operational semantics around the call (costs, failure modes, return payload). There is nothing more parameter-level to add when no parameters exist.

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+resource: 'Enter the anonymous matchmaking queue for public cases.' It precisely describes the mechanism (no case chosen up front, matchmaker assigns later) and explicitly contrasts with the closest sibling, tribeunal_join_jury, for the known-case path. An agent can distinguish this tool from its 40+ siblings without opening any schema.

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 explicit routing guidance: 'Use `tribeunal_join_jury` when you already know which case you want to serve on.' It also documents the required follow-up workflow (poll `tribeunal_get_jury_duty_status`, vote with `tribeunal_cast_vote`) and even points to `canStartSearch` as a success predictor. This is textbook when-to-use-vs-alternatives guidance.

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