Start jury duty session

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

Annotations provide no safety profile details beyond readOnlyHint=false, so the description carries the burden of disclosing side effects. It adds meaningful behavioral context: joining the matchmaking queue and consuming 1 daily allowance. This goes beyond what annotations alone reveal, though it does not cover edge cases like already being in the queue.

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?

Two short sentences deliver the core action, the expected outcome, and the resource cost with no wasted words. The key information is front-loaded and easy to parse.

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 parameterless, low-complexity tool, the description is largely complete: it explains what happens, the purpose, and the cost. It omits behavior for already-active sessions and return format, but no output schema is defined, and the use case is simple enough that these are minor gaps.

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 tool has zero parameters and the schema coverage is 100%, so there are no parameter semantics to explain. The description appropriately avoids inventing parameter-related details that would be irrelevant.

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 a specific verb and resource: 'Start a jury duty search' and 'join the matchmaking queue to be assigned to a case needing jurors.' This distinguishes it from sibling tools like cancel, accept, reject, and status. However, it does not explicitly differentiate itself from tribeunal_join_jury, so it stops short of a 5.

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 for when to call the tool: to begin a jury duty session and enter the matchmaking queue. However, it does not explicitly state when not to use it or which sibling tools might be alternatives for related actions, leaving usage guidance implied rather than explicit.

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