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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description is not obligated to restate it. It adds genuine value beyond that: an enumeration of returned evidence types and, importantly, a liability disclaimer ('Allegations and procedural status are not findings of liability') that shapes how an agent should interpret and report the data. Pagination behavior for limit/offset is not disclosed.

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?

Three tight sentences, front-loaded with what the tool returns and followed by the interpretive caveat. No filler, though the middle sentence's field enumeration is dense enough that it could be trimmed without losing meaning.

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?

With no output schema, the description usefully enumerates returned fields (jurisdiction, agency, case identifiers, status, dates, parties, source evidence), which is the right call. However, it omits any parameter guidance and pagination semantics for a 3-param tool, leaving the input side under-specified.

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 0%, so the description carries the full burden for three parameters, yet it never mentions symbol, limit, or offset. An agent cannot learn from the description what identifier format is expected or that results are paginated. This is a clear compensation 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 resource (company litigation and antitrust dockets) and a distinguishing mechanism (linked through verified corporate identities), which separates it from generic sibling tools like sec.filings or news.stories. The retrieval verb is implied rather than stated, and it does not explicitly contrast itself with the nearest sibling (sec.filings), 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?

There is no when-to-use guidance, no exclusions, and no named alternatives despite ~40 sibling tools that could plausibly overlap (sec.filings, news.stories, catalysts.event). The purpose implies a use case but the agent is left to infer the trigger condition entirely.

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