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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about the data source and court coverage, but does not explicitly state that the operation is read-only, nor does it mention pagination, result limits, or any side effects. The description is adequate for a search tool but lacks deeper behavioral details.

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 compact, front-loaded with the primary action, and consists of two sentences with no redundant information. Every phrase contributes value: 'Search 1.1 million+ US federal and state court opinions via CourtListener' and the coverage note.

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 provides the essential context (source, scope, coverage) but omits the fact that the tool also supports docket search via the 'type' parameter, and it does not describe the response format (no output schema exists). These gaps make it incomplete for a tool with optional parameters and no return value documentation.

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?

The input schema has 100% description coverage for all three parameters (type, limit, query), so the baseline is 3. The description adds context regarding the scope and source of the search, which indirectly informs the 'query' parameter, but it does not add new parameter-specific meaning beyond the schema.

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 ('US federal and state court opinions') with a distinct scope ('1.1 million+', 'Covers Supreme Court, Circuit Courts, District Courts'). It also names the data source (CourtListener/Free Law Project), which differentiates it from sibling tools that may cover different jurisdictions or sources.

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 clearly implies when to use this tool: when searching for US court opinions. It provides context about the coverage and source, but does not explicitly mention alternatives or when not to use it. Nonetheless, the context is clear enough for an agent to select this tool over unrelated siblings.

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