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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety and side-effect profile. The description adds value by detailing the return fields and providing a concrete usage example, but it does not disclose any further behavioral traits (e.g., rate limits, timeouts). This matches the bar where annotations carry most of the load.

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 three sentences: purpose, scope, and a concrete example. It is front-loaded with the core action and immediately useful information. Every sentence earns its place with no redundancy or fluff.

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 compensates by listing the returned fields and giving a worked example. It also clarifies the coverage scope. It does not mention potential pagination details beyond the offset parameter (which is in the schema) or any limitations, but for a read-only search tool this is sufficiently complete.

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 all four parameters are already documented. The description reinforces the `_apiKey` format with an example and implies the `q` syntax via the example, but does not add substantial meaning beyond the schema. Baseline 3 is appropriate when the schema is exhaustive.

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 opens with a specific verb and resource: 'Search court dockets (state + federal)'. It further clarifies scope ('675M+ US state, county, and federal court dockets') and explicitly differentiates from CourtListener ('deeper state coverage'). It also lists the return fields (court, docket number, title, filing date, link), making the tool's purpose unmistakable and distinct from siblings like docketalarm_get_docket.

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 makes the tool's context clear—it is for full-text searching across many dockets—and the sibling names (docketalarm_get_docket, docketalarm_search_pacer) imply when alternatives are appropriate. However, it does not explicitly state when not to use this tool or name an alternative, so it earns a 4 rather than a 5.

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