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

Goes beyond the read-only/idempotent annotations by disclosing that this is a periodically refreshed snapshot whose response carries data_as_of, that a no-match response names the filters tried, and that it is keyless. This is meaningful behavioral context, though it omits rate-limit or latency details.

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?

Dense but front-loaded: purpose first, then required inputs, then return contents, then sibling differentiation and freshness. Every sentence carries information, though the prose is packed enough to be slightly harder to scan than necessary.

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 supplies the return shape (filing/termination dates, nature-of-suit/offense code, disposition, party names, judgment amount, sentence terms), snapshot freshness semantics, no-match behavior, and keyless access. An agent has everything needed to call it correctly.

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%, so the baseline is 3. The description reinforces that docket and district/circuit use FJC's own formats rather than PACER, which adds a useful nuance, but it doesn't mention the optional fiscal_year or defendant_number parameters and adds little beyond the schema text.

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?

States a specific verb and resource ('look up a SPECIFIC federal case or criminal defendant by docket number') and scopes it to the FJC IDB across three case types. It explicitly distinguishes itself from court-listener, which holds docket text and filings rather than statistical-outcome records.

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?

Clearly frames the use case (you have a docket number and want the statistical-outcome record) and names court-listener as the complementary tool for docket text. It does not explicitly contrast with the sibling fjc_case_outcomes_summary, so the exclusions are incomplete, but the context is clear.

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