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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, lowering the bar. The description still adds genuine context beyond them by disclosing the ~11-month window for closures and the aggregation granularity (motion family), though it says nothing about coverage limits or freshness of verdict data.

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?

A single front-loaded sentence with no filler; the parenthetical time window earns its place. Slightly dense in its list of three metrics but not padded.

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-value detail need not be spelled out, and the description adequately characterises what the profile covers. Minor gap: no statement of jurisdictional/dataset scope, which matters for an open-ended analytics 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% for both parameters, so judge_key and purpose are already documented in structured data. The description adds no meaning beyond the schema, so the baseline of 3 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 names a specific resource (one judge) and enumerates the three content areas returned: case outcomes/closures, motion grant rates by family, and trial/verdict figures. It is clear what the tool does, though it never names a sibling (e.g. search_judges) to contrast scope.

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?

Usage is only implied: the schema notes judge_key comes 'from search_judges', suggesting this is the detail lookup after a search, but the description itself states no when-to-use condition or alternative. An agent must infer the search-then-fetch pattern.

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