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

With no annotations, the description must carry the full burden, and it usefully discloses two behavioral facts an agent cannot get from schema: credential 'none' and cost 'free'. It also describes the returned content, compensating for the absent output schema. It stops short of stating read-only semantics or freshness/pagination behavior.

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?

Tight and front-loaded: scenario first, then the returned data, then credential and cost. Every fragment carries information. The 'I want to see...' phrasing is slightly informal but functions as a clear user-intent opener.

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 one-parameter read tool with no annotations and no output schema, the description covers the key gaps: it lists the data returned and states the auth/cost profile. The only missing piece is parameter-level detail for matterId, which is minor given its self-documenting name.

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 0%, so the description ideally should compensate, but it only gestures at 'a particular case' without naming or explaining matterId's format. The single required parameter is self-evident from its name, keeping this at a minimum-viable 3 rather than lower.

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 resource (a particular case/matter) and enumerates what it exposes: status, written arguments, procedural steps, and judgments. This lets an agent tell it apart from list_matters, though it never explicitly names that sibling. A clear verb+resource but short of full sibling differentiation.

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 leading sentence frames the scenario ('I want to see what has happened in a particular case'), implying when to reach for it, but gives no when-not conditions and does not point to alternatives like list_matters or read_judgment. Usage is implied rather than guided.

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