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

Annotations already declare readOnlyHint/destructiveHint=false, and the description adds real context beyond them: the return statistics (deliveredCount, readCount, lastUsedDT) and the permission-dependent scope where memory:moderate expands coverage to all company records except personal ones.

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-loads the core action, then statistics, then use cases. It is dense and semicolon-heavy in the second half but every clause carries information; no filler.

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 12 params and no output schema, the description usefully names the returned statistics and explains the permission-scoped coverage, which compensates for the missing output schema. Remaining filter semantics are left to the schema, which is acceptable.

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%, and much of what the description says about verified, sort, and unusedDays restates the schema. Its incremental value is combining them ('sort = usage with unusedDays') and implying level scope, but many of the 12 parameters (IDs, jobs, load, query, shared, authorUID, projectID, repositoryID) get no semantic help.

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 and resource ('Lists agent memory records visible to the user') plus the scope of visibility, and it clearly differentiates from siblings like memory_read, memory_create, and memory_update by framing it as a filtered list with usage statistics.

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?

Gives concrete use cases (finding duplicates before saving, reviewing, moderating, cleaning up) and conditional semantics (verified = false is the moderation queue; sort = usage with unusedDays finds rarely used records). It does not explicitly name an alternative tool to use instead, which keeps it short of a 5.

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