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

With no annotations, the description carries the whole burden. It usefully discloses output shape (ranked cases with INSC citations, one-line holdings, treatment signals) and ranking behavior, but says nothing about permissions, pagination, result caps, or that it is a read-only operation.

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 tight sentences, front-loaded with the verb and resource, followed immediately by the return shape. Every clause earns its place with no boilerplate.

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 the tool searches and roughly what it returns, which is reasonable for a simple two-parameter search. But with no annotations, no output schema, and an undocumented limit parameter, it is not fully sufficient for an agent to know result caps or when to pivot to sibling tools.

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 50%: the query parameter is documented in the schema, and the description adds that it accepts natural-language issues, keywords, or legal propositions, which is meaningful. However, the limit parameter (default 5, max 15) is undocumented in both schema and description, leaving a real gap.

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 verb and resource ('Search the insc.one Supreme Court index') and enumerates the accepted query modes (natural-language issue, keyword, legal proposition). It does not explicitly differentiate itself from siblings like check_treatment or get_ratio, though the search scope makes it naturally distinct.

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?

There is no guidance on when to use this tool versus check_treatment, get_ratio, or resolve_citation, nor any preconditions or exclusions. The agent must infer that this is the entry point for discovery while siblings handle follow-up operations.

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