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 without description help. The description adds only that results are suggestions intended to feed a subsequent filter, which is mild context; it says nothing about how matching works (prefix vs substring), ordering of results, or what happens with an empty/ambiguous q. Given the annotated baseline, a 3 is appropriate.

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 usage directive is front-loaded in the first sentence, the routing instruction second, and per-parameter detail is quarantined in a structured Args block. Every line contributes; there is no filler or restatement of the tool name.

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?

An output schema exists, so return values need not be explained, and the description fully specifies the three inputs for a simple three-parameter lookup tool. The remaining gap is competitive positioning against the sibling autocomplete_citations, which an agent may need to disambiguate.

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 0%, so the description carries the full burden and does so: field's three permitted values are enumerated with glosses ("claimant" = applicant/claimant/appellant side, "respondent" = defendant side, "judge"), q is illustrated with a concrete expansion example ("Lamb" → "London Borough of Lambeth"), and limit states both default (10) and ceiling (25). This is meaningfully more than the bare schema titles provide.

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?

"Get name suggestions for party or judge filters" gives a concrete verb (get suggestions) and a bounded resource scope (party/judge name filters), so the tool's function is unambiguous. It stops short of a 5 because it never distinguishes itself from the sibling autocomplete_citations, which an agent could easily confuse with a similarly named suggestion tool.

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?

"Use this before filtering search_cases to find the correct spelling / full name" explicitly names the downstream tool and the sequencing condition, which is exactly the kind of routing guidance an agent needs. There is no explicit when-not guidance or mention of the alternative autocomplete tool, so it falls short of a 5.

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