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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral detail: the scope is the signed-in user's institution, results are ordered soonest hearing first, and the default filter is active. It stops short of pagination or result-count 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?

Two sentences, front-loaded with the resource and scope, then the returned fields, ordering, and filter. Dense but every clause carries information; the trailing 'Use for...' sentence is the only slightly soft element.

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 helpfully enumerates the returned fields (forum, bench, case number, stage, next hearing, last update, claim amount) and ordering, which is exactly what an agent needs. For a read-only single-enum-param list tool this is nearly complete; pagination/limits remain unspecified.

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 single enum parameter is fully documented in the schema itself, so the base score is 3. The description restates the same three status values and default without adding syntax or edge-case meaning beyond the schema.

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 (lists) and resource (matters on the panel matter register) with scope (signed-in user's institution) and enumerates the returned fields plus sort order. An agent can distinguish it from siblings like get_matter_status or upcoming_hearings without opening the schema.

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 final sentence gives a usage context ('overview of the institution's matters with its panel counsel') and the status filter semantics are explained, but no alternatives such as upcoming_hearings or get_matter_status are named, and no when-not-to-use is stated. Usage is implied rather than routed.

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