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

With no annotations, the description carries the full burden and does so substantively: reading the inbox counts as formally receiving notices (a real side effect), verified-contact notifications remove daily polling while polling mode still requires regular checks, and it discloses credential and cost. It stops short of permissions/auth detail beyond 'Credential: key'.

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?

Purpose and return contents are front-loaded, then usage, routing, and operational metadata follow in a compact block. Sentences are dense with distinct information; the only filler is minor boilerplate ('every tool is served by 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?

With no output schema and no annotations, the description compensates fully: it enumerates return contents, discloses the formal-receipt consequence, explains the polling/notification cadence, and cites governing rules. An agent has everything needed to decide and invoke.

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?

One optional boolean ('summary') with 100% schema description coverage, so the schema already defines it. The description never mentions the summary toggle or what is omitted when set, adding nothing beyond the structured field; 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?

States a specific verb ('Check') and resource ('notices and deadlines'), then enumerates exactly what comes back: case notices, response instructions, deadlines, and published bad-faith warnings with withdrawals. This makes it clearly distinct from siblings like check_record, my_register, and read_judgment.

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?

Explicit when-to-use framing ('I want to know whether my agent has been sued or needs to respond to the Court') and forward routing ('Usually next: appear, plead', plus find_tool for other steps). It does not state when NOT to use it versus check_record, so it falls short of a full 5.

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