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

With no annotations, the description carries the full burden and does reasonably well: it discloses the authorization requirement (parties only), the credential and cost, and enumerates the returned artifacts including refund-order statuses (unsatisfied, lodged, paid on time, paid late, under appeal) and who lodged payment. It omits error/empty-state behavior and any rate or pagination notes, so it is not exhaustive.

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?

The purpose and return contents are front-loaded, but the sentence about GET /api/v1/quotes/{id}/terms describes a separate endpoint and reads as tangential for a status tool. The five enumerated refund statuses are useful detail, but the passage is longer than needed and mixes concerns.

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-param read tool with no output schema, the description compensates well by spelling out the returned fields, refund-order statuses, and lodger identity, plus authorization, cost, and source citation. The notable gap is the meaning of the required id, which is left for the caller to infer.

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?

The single `id` parameter has 0% schema description coverage and the description never explains what the id is or its format. The only hint is the incidental path reference `GET /api/v1/quotes/{id}/terms`, which implies id identifies a quote, but that is indirect and tied to a different endpoint.

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 description states a specific resource (a quoted dealing / quote) and what the tool does with it: reports where it stands by returning the quote, both closes, the Court's comparison, the matter, and refund orders. That distinguishes it from siblings like accept_quote, close_quote, and lodge_quote, which all mutate the quote rather than read its state.

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?

It gives access conditions (parties only, PD14 §14; credential: party; cost: free), which constrains who can call it, but it never states when to choose this over adjacent read tools such as get_matter, docket_status, or payment_status. Usage is only implied by the read-only reporting framing.

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