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

Annotations already establish the safety profile (read-only, idempotent, non-destructive, closed-world), so the description isn't carrying that burden. It adds real behavioral value instead: records come back as latest version with full content, include a status, and absent facts are null and listed in `missing` — with an explicit instruction not to fabricate them.

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?

Three sentences, front-loaded with the core action and scope, then the highest-value warning last. Dense but every sentence carries distinct information; the two account/organization cases are necessarily separated.

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 and no params, the description proactively characterizes the returned content (full content, latest version, status, null `missing` fields), which is exactly what an agent needs. Complete for this simple read tool, though it leaves the shape of the `missing` indication implicit.

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?

Zero input parameters, so the baseline is 4. The description references `missing` and `record_id`, clarifying the identity/data semantics an agent must understand when following up, which is useful even though these aren't input parameters.

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 ('records of processing activities (GDPR art. 30(1))'), and clarifies scope for both individual accounts and client organizations (whole register with status). It does not explicitly contrast itself with the write counterpart save_processing_record, but the read/write distinction is self-evident from the verb.

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?

Usage is implied rather than stated: the tool is for reading the register, and the closing instruction to 'save the record with its record_id' hints at the save_processing_record path. There is no explicit when-to-use/when-not or named alternative, so it stays at implied guidance.

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