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

readOnlyHint=true already tells the agent this is a safe read, so the description isn't carrying the safety burden. What it does add is the shape of the response — status narrative, next human step, business-hour target, lawyer question — which has value because no output schema exists, but it says nothing about freshness, polling behavior, or what happens with an invalid/expired token.

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?

A single compact sentence-fragment with no filler, front-loading the most important element (where the matter stands). It is tight, though its telegraphic phrasing ("the target in business hours") costs clarity rather than words.

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 is the only source of return-value information, and it nominally covers the four things returned. But it is too terse to fully serve that role: "the target in business hours" is ambiguous (target date? SLA?), and nothing is said about error handling or whether the status changes over time.

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% and both parameters are documented as coming from open_matter, so the schema does the work. The description adds no information about matterId or matterToken (e.g., token being single-use), so 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?

The name and title say "matter status," but the description itself never states a verb or that it retrieves anything — it reads as a bare list of returned fields ("Where the matter stands, the next human step, the target..."). An agent can infer it reads a matter's status, but the purpose is only implied and no sibling is distinguished.

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?

There is no indication of when to call this versus alternatives such as get_deliverable or get_requirements, nor any prerequisite (e.g., that a matter must first be opened). The mention of the lawyer's question hints at a polling/check-in use case but never states it.

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