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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered without description help. The description adds genuine domain semantics — that jurisdictions carry their own laws and world — which helps the agent reason about downstream tools, but it says nothing about return shape, ordering, or whether the set is static.

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, front-loaded with the resource definition. Both sentences carry weight, though the second is domain color rather than operational guidance, which keeps it just under a 5.

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?

With no output schema, no parameters, and rich annotations, the description covers the conceptual identity of a jurisdiction but never indicates what a returned entry looks like (identifier? name? nested world/law references) or how many exist. For a simple enumeration tool that is a tolerable but real gap.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-related content is needed or missing.

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 the precise resource ('the jurisdictions MuseCourt serves') and frames it against a related sibling concept (cases), so an agent knows this returns the set of jurisdictions. It stops short of a 5 because it is phrased as a noun clause with the list verb only implied by the tool name, and it does not explicitly distinguish itself from get_laws or get_world_identity_challenge, which are adjacent domain concepts.

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?

There is no explicit when-to-use statement, no prerequisites, and no alternative named (e.g., get_laws for the law content of a jurisdiction). The clause 'Each case belongs to one' faintly implies this is a lookup you need before filing or interpreting a case, but the agent must infer that routing itself.

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