Decline jury invitation

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds useful behavioral context: the action is not just a rejection but also returns the juror to the queue for a different case. This goes beyond the bare 'reject' concept.

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 description is a single sentence with the core action stated first and the consequence immediately following. There is no filler, repetition, or unnecessary detail.

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 one-parameter destructive action with annotations, the description gives enough to understand the operation and its immediate effect. It could mention prerequisites like whether an active assignment is required, but the invocation context is otherwise complete.

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 schema fully documents memberId as 'Member ID from the jury assignment' with 100% coverage. The description does not add parameter-specific guidance, but with full schema documentation, baseline 3 is appropriate.

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 names a specific action ('Reject') and a specific resource ('jury duty assignment'), and adds a meaningful consequence ('return to the queue for a different case'). This clearly distinguishes it from sibling tools like jury_duty_accept or jury_duty_cancel, even without naming them explicitly.

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 clearly places the tool in the context of declining a jury assignment and being requeued. It does not explicitly state when not to use it or name alternatives such as cancel/accept, but the context is clear enough for an agent to select it for the rejection flow.

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