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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint. The description adds meaningful context beyond those: the data is public domain, results include CAP ids and citations, and the v1 index only covers the U.S. Reports reporter. This is valuable behavioral transparency and does not contradict the annotations.

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 three sentences with no filler: purpose first, then output and next-step guidance, then a critical scope caveat. It is front-loaded and every sentence contributes useful 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?

The description covers what is searched, what is returned, how to retrieve full opinions, and a major index limitation. The schema handles parameter details. It stops slightly short of stating whether at least one search criterion is expected or describing the exact result envelope, but for a search tool with strong annotations this is a minor 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?

Schema coverage is 100%, with each parameter already described and exemplified. The description adds a useful high-level grouping of filters and the decision-date range concept, but does not need to compensate for missing schema documentation.

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 states a specific action and resource: searching US court opinions from the Caselaw Access Project by case name, keyword, court, jurisdiction, and date range. It clearly differentiates itself from the sibling caselaw_opinion_text by describing its metadata output and directing the agent to that sibling for full opinion text.

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 an explicit follow-up/alternative: 'Use caselaw_opinion_text with a returned id to read the full opinion.' It also sets expectation with the v1 U.S. Reports coverage note. However, it does not explain when to prefer other sibling search tools such as caselaw_citation_lookup or court_opinion_search.

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