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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context beyond that: the permission (memory:moderate) changes the visible scope, and it discloses the usage-stat fields returned (deliveredCount, readCount, lastUsedDT). This is meaningful for a list tool with no output schema.

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?

Front-loaded with the core action, then usage and parameter recipes. The second sentence is dense with several clauses, but each clause (moderate scope, moderation queue, cleanup pattern) contributes distinct, actionable information rather than padding.

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 12-parameter list tool with no output schema, the description covers the conceptual model (record visibility), the key returned stats, and the two dominant workflows. It is close to complete; minor gaps are parameters like load/shared/level that neither schema nor description illuminate.

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 coverage is 67%, so several parameters are already documented. The description adds interpretation the schema lacks: verified=false identifies the moderation queue, and the sort=usage + unusedDays pairing is explained as a rarely-used-records finder. It leaves some params (load, shared, level) implicit, keeping it below a 5.

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 ('Lists agent memory records visible to the user') and adds scope via 'with filters and usage statistics'. It is distinguishable from siblings like memory_read (single record by ID) and memory_create/delete, though it doesn't name those siblings explicitly.

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 concrete when-to-use context: 'reviewing, moderating and cleaning up memory', with the moderator pattern (memory:moderate scope, verified=false = moderation queue) and the cleanup pattern (sort=usage with unusedDays). It stops short of naming the alternative sibling (memory_read) for single-record retrieval.

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