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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds a behavioral note about cost ('Cached documents are free'), which hints at pricing implications for non-cached data, but it does not mention rate limits, auth handling beyond the schema, or pagination behavior, so it modestly exceeds the annotation baseline.

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 two sentences plus an example, front-loading the core action ('Get full docket detail') and following with return contents and a noteworthy cost detail. Every sentence contributes useful information and there is no filler.

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 read-only retrieval tool with three well-documented parameters, the description is largely sufficient: it names the return payload and includes an example. The absence of an output schema is partially offset by the listed return fields, but it lacks any guidance on pagination or error conditions, which keeps it from being fully 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?

The schema covers all three parameters with full descriptions, setting the baseline at 3. The description does not add new parameter-level semantics beyond an example invocation that matches the schema's own example, so it adds no additional meaning.

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 states a specific verb 'Get' and resource 'full docket detail' for a case, enumerating the returned fields (case title, parties, filing date, docket entries) and scoping it to 'a specific court + docket number.' This clearly distinguishes it from sibling search tools like docketalarm_search, which locate cases rather than retrieve a known one.

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 implies the tool is for retrieving a known case by court and docket number, and includes a concrete example, but it never explicitly contrasts it with docketalarm_search or states when not to use it. It provides clear context without explicit exclusions or alternative routing.

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