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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by enumerating the docket contents (allegations, status, date, participants, activity log, election tally) and giving concrete answer examples. It does not mention error handling for invalid case numbers, but the annotation coverage plus detailed output scope justifies a 4.

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 front-loaded with the core purpose ('Full docket for one ... case by case number'), then provides examples, contents, and sample queries. It is longer than minimal but every sentence adds value. No tautology or fluff, so a 4 is justified.

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 single-parameter retrieval tool with strong annotations, the description is comprehensive. It specifies the exact resource, lists the full range of returned data, and gives example user questions. There is no output schema, but the description clearly communicates what the tool can answer. Nothing an agent needs to invoke it correctly is missing.

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% and the schema already describes the case_number format, case-insensitivity, and whitespace handling. The tool description reinforces this with two concrete examples ('10-CB-393760', '31-RC-357638') and context about being case numbers, but adds no meaning beyond the schema. Baseline 3 is appropriate.

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 the specific verb and resource: 'Full docket for one US National Labor Relations Board case by case number.' It lists exactly what's included and explicitly contrasts with the sibling tools via the 'by case number' qualifier, distinguishing it from nlrb_search and nlrb_recent_filings. Example queries further clarify the purpose.

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 clearly indicates usage when a specific case number is known ('by case number') and provides example queries. However, it does not explicitly name sibling tools or state when not to use this tool (e.g., when searching by party name or listing recent filings). This is clear context without exclusions, warranting a 4.

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