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

With no annotations, the description carries the full behavioral burden. It reveals the data sources and the read-only nature implicitly, but says nothing about pagination, result ordering, rate limits, or coverage gaps between opinions and the RECAP archive. That is a thin behavioral disclosure for a search tool.

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 short sentences with the purpose and filter capabilities front-loaded and no wasted wording. It errs slightly toward being sparse rather than verbose, which is the right direction.

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 five-parameter search tool with no annotations and no output schema, the description covers the essentials but leaves the agent guessing about result shape and pagination, and its 'case type' phrasing may mislead about the `type` parameter. Adequate but with clear gaps.

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 restates the court and date filters, but its mention of 'case type' does not correspond to any parameter (the `type` param is result type o=opinions), which adds a slight inaccuracy rather than new meaning.

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?

States a specific verb (Search) and resource (federal court opinions and cases) and names the underlying data sources, CourtListener / RECAP Archive. It does not explicitly differentiate itself from siblings like get_case or get_company_cases, but 'search' versus 'get' is a clear enough distinction.

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 mention of filtering 'by court, date, and case type' implies the intended usage context, but there is no explicit when-to-use/when-not guidance and no alternatives are named. An agent must infer that this is the broad discovery tool and get_case is for retrieving a known case.

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