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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the return shape ('case summaries with citations') and the federal/state coverage scope, which is helpful, but it does not disclose pagination, result limits, ordering, or coverage caveats beyond that.

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 description is a single efficient sentence that front-loads the search scope and filter options, then states the return format. There is no filler or redundant repetition of schema details.

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?

The description is adequate for a read-only search tool: it states what is searched, which filters matter, and what is returned. However, it lacks guidance on distinguishing this sibling from other court-search tools and does not mention result limits or pagination behavior, making it only minimally complete for a tool with 7 parameters and no output schema.

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 description coverage is 100%, so the baseline is 3. The description enumerates keyword, court, judge, party name, and date range, which maps cleanly onto the schema properties, but it does not add meaning beyond what the schema already provides, such as query syntax or filter combination behavior.

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 uses a specific verb ('Search') and clearly identifies the resource ('federal and state court opinions') plus the main filter dimensions. It does not explicitly distinguish this tool from closely related siblings like court_opinion_search or caselaw_search, so it falls short of a 5.

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 implies the tool is for finding court opinions by common legal filters, but it provides no explicit guidance on when to prefer this over alternatives such as court_opinion_search, caselaw_search, court_docket_lookup, or court_judge_lookup. There are no exclusions or 'use X instead' signals, which is a notable gap given the large sibling set.

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