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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, but the description adds valuable context by specifying exactly what persists (case, docket history, passport, mail address) and that only monitoring stops. This goes beyond the annotations and gives the agent a clear mental model of the side effects.

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 action and usage triggers, and then the non-destructive note. Every sentence earns its place with no filler or redundancy.

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 tool with one optional parameter and a simple, well-defined behavior, the description fully covers what the tool does, when to use it, and what remains untouched. The absence of an output schema is fine because the tool likely returns nothing meaningful beyond a success signal, and the description is sufficient for correct invocation.

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 parameter matter_id is fully described in the schema (100% coverage), including guidance to omit it when only one case is followed. The description does not add extra param detail, but the schema already does the job, so a baseline score of 3 is appropriate.

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 clearly states the verb 'stop' and the resource 'monitoring of a saved case', and it distinguishes itself from the sibling watch_case by explicitly noting that the case, docket history, Case Passport, and CaseMail address all remain. This leaves no ambiguity about the tool's function.

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 description provides explicit trigger phrases ('stop monitoring', 'stop alerts', 'pause watching', 'unfollow a case') and clarifies what does not happen, making it obvious when to use this tool versus watch_case. It is direct and actionable.

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