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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about rules being extracted from standing orders and practices documents, but it does not disclose return format, pagination, or empty/error behavior. This is adequate for a safe read but not richly transparent.

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 efficient sentences with the main action front-loaded and no filler or repetition of parameter names or title. Every sentence contributes meaningful information.

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 simple read-only retrieval with two well-documented parameters and annotations covering the safety profile, the description is nearly complete. It gives the source of the rules and the judge-specific scope, though it stops short of describing the response shape or how this relates to the sibling search_filing_rules tool.

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?

Schema coverage is 100%, and both parameters (judge_slug and district_id) already have descriptive examples in the schema. The description adds no parameter-specific meaning beyond restating the judge scope, so the baseline score of 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 verb and resource ('Get all extracted rules') and clearly scopes it to 'a specific judge.' The source attribution to standing orders and individual practices documents distinguishes this from broader rule-search siblings, so an agent can identify what the tool does without opening the schema.

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: use this when you need all extracted rules for one judge, not for generic filing-rule searches. It does not explicitly name alternatives or state when not to use it, which keeps it slightly below a 5.

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