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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint. The description adds real value beyond them by stating the required "review pending memories" permission, which an agent cannot see in the schema. It stops short of explaining pagination behavior or whether the list is empty-safe.

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 short sentences, scope stated first and the permission requirement second. No filler or redundant restatement of the tool name.

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?

An output schema exists, so return-shape explanation is unnecessary, and the permission prerequisite is covered. The main gap is the undocumented `page` parameter and absence of any paging expectation for a list tool that is likely paginated.

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 only 50%: `clone_id` is documented in the schema, but `page` has no description anywhere. The description mentions neither parameter and gives no guidance on paging through results or when to supply `clone_id`, so it fails to compensate for the coverage gap.

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 names a specific verb and resource ("List memories") plus a clear scope qualifier ("waiting for the owner's review"), which separates it from `remember` and `consult_mind`. It does not explicitly distinguish itself from the sibling `review_pending_memory`, leaving the list-vs-act distinction to inference.

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 clause "so the owner can go through them with you" implies the workflow context, and the permission sentence gives a prerequisite. However, there is no explicit statement of when to use this versus `review_pending_memory` (which presumably acts on a single item), and no exclusions.

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