Jury duty status

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Get' without contradicting it. It adds useful context by listing the specific status fields returned, which is important since there is no output schema. It does not disclose edge-case behavior (e.g., response when no jury request exists), but for a read-only status endpoint this is a minor gap.

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?

The entire description is a single, front-loaded sentence with no filler. Every phrase conveys a distinct piece of information: status, queue position, and active search/assignment.

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 no-parameter read-only status tool, the description covers the essential return values, especially given the absence of an output schema. It could be more explicit about default behavior when no jury request exists or about the scope (current user), but the meaning is largely inferable from the wording.

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 has zero parameters and 100% coverage, so the baseline is 4. The description appropriately adds no parameter details since there are none to describe.

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 uses a specific verb ('Get') and names the exact resource ('current jury duty request status') plus concrete data points returned (queue position, active search/assignment). This clearly separates it from mutation siblings like tribeunal_jury_duty_start or tribeunal_jury_duty_cancel, though it does not explicitly distinguish from the similarly-named tribeunal_jury_duty_dashboard.

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 implies the tool is for checking status but provides no explicit when-to-use guidance or alternatives. With siblings like tribeunal_jury_duty_dashboard, tribeunal_jury_duty_history, and tribeunal_get_current_user, an agent must infer when this specific status check is the right choice.

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