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

Annotations already cover read-only, idempotent, non-open-world, non-destructive behavior. The description adds valuable domain context beyond that: the causal trigger (a new rule), what fields are returned (rule, source, reason), and the lifecycle rule that saving a new version closes reviews. It also discloses the paywall constraint (paid plans), which is not in annotations and could affect invocation. It does not describe pagination or ordering.

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?

One compact sentence that front-loads the action and scope, followed by two short clauses adding only the lifecycle and plan constraints. No wasted words or repetition of the title.

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 parameters, no output schema, and annotations covering safety hints, the description is close to complete. It adds the domain trigger, returned fields, closure behavior, and login/plan implications. It could mention ordering or whether results are paginated, but those are minor omissions.

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?

There are zero parameters, so there is no parameter semantics to explain; the baseline for zero params is 4. The description does not claim to accept filters, which correctly matches the empty 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?

The description states a specific verb and resource: it lists records of processing activities, and further specifies the triggering condition (a new rule that may affect them) and what is shown for each (the rule, its source, the reason). This clearly distinguishes it from siblings like list_processing_records and save_processing_record.

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 makes the 'when' clear: after a change in the law, to see which records need review. It also implies the lifecycle boundary (saving a new version closes reviews), which tells the agent when reviews stop appearing. It does not explicitly name an alternative tool or state when NOT to use this one.

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