Jury duty dashboard

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

Annotations already mark the tool as read-only, so no destructive side effects need explaining. The description adds value by disclosing what the response will contain and clarifies that case assignments are cases to vote on, which is useful behavioral context.

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 compact sentences, each earning its place: the first states the action and content, the second sharpens selection. There is no repetition of the schema or filler.

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 parameter-free, read-only dashboard with no output schema, the description communicates the return contents and the primary use case clearly. An agent can decide whether to call this tool instead of the more specific jury-duty siblings.

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 is no parameter-level burden for the description to carry. The baseline for parameter-free tools applies.

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 starts with a concrete action and resource ('Get jury duty dashboard') and enumerates the dashboard's contents: case assignments, allowance info, active request status. The closing line ('Best tool for finding cases assigned to you') makes its purpose unmistakable and separates it from the surrounding jury-duty siblings.

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?

It gives a clear usage context and a selection rule: use this when you need cases assigned to you. It does not explicitly name alternative tools or say when not to use it, but the dashboard's composite scope is enough to guide an agent.

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