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

With no annotations, the description carries the full burden and does a decent job: it discloses credential requirements (none) and cost (free), and describes the shape of returned content. It does not explicitly declare read-only semantics or error behavior, but the auth/cost disclosure is genuine value beyond the schema.

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?

Short and front-loaded: purpose first, then the use condition, then credential/cost. Slightly redundant between 'Check a case's progress' and 'Shows the case's status...', but no filler and every element has a role.

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 read tool with full schema coverage and no output schema, the description is nearly sufficient: it enumerates return content and covers access/cost. Only the absence of any sibling differentiation 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?

Schema description coverage is 100%; the matterId field already explains it is a UUID sourced from file_claim, the notice URL, or list_matters, and warns it is not the file number. The description adds nothing on top of the schema, so the 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+resource ('Check a case's progress') and enumerates what it surfaces: status, written arguments, procedural steps, and judgments. Clear on its own, but it never distinguishes itself from siblings like read_judgment or check_record that could plausibly return overlapping case material.

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?

Provides an explicit trigger ('Use it when: I want to see what has happened in a particular case'), giving the agent a concrete context to select it. It lacks any when-not guidance or named alternatives, so it stops short of a top score.

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