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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the shape of the payload (counts, top NOS, recent cases), which matters since no output schema exists, but it omits how "recent" is bounded, whether the lookup is fuzzy, and pagination limits.

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: the returned fields are front-loaded, and the payoff questions are given last. No filler, no restatement of the tool name.

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 one-parameter read tool with no output schema, the description does the important work of telling the agent what comes back and why it would be called. The remaining gap is that "recent" is undefined and there is no routing to the sibling courts_recent.

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% and the single name parameter is fully documented in the schema, including the substring-match behavior. The description adds only that the scope is "one company," which restates what the schema already conveys; baseline 3 applies.

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 (a company's litigation docket) and enumerates what it returns: docket count, top Natures of Suit, recent cases. It never names or contrasts with the obvious sibling courts_recent, so an agent must infer the entity-vs-recency split from the tool name alone.

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 framing questions ("is this company being sued?", "for what?") imply the use case clearly, which is better than nothing. However, there is no explicit when-not guidance and no pointer to courts_recent or dossier for the temporal or aggregate alternatives.

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