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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the brain-scoping context but omits notable behavior such as archived memories being excluded unless includeArchived is set, plus any ordering or result-size limits.

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?

A single front-loaded sentence with no filler; the core action and its optional filters lead. It is efficient, though brevity here coincides with the missing detail noted in other dimensions.

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, the description carries the burden of explaining what a listing returns, and it does not: no ordering, no pagination, no indication whether archived items are omitted. For a four-parameter read tool in a crowded family, this is the minimum viable.

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 75%, so most parameters (type, brain, concept) are self-documenting. The description only restates 'type or concept' and never addresses includeArchived, the one parameter lacking a schema description, so it adds little beyond the 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?

States a specific verb ('Lists') and resource ('memories') with the scoping dimension ('in a brain'). However, it does nothing to separate itself from near-siblings like memory_search, memory_get, and recall, so an agent must infer which of the listing/retrieval tools fits.

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?

No when-to-use or when-not-to-use guidance is given, and no alternatives are named despite memory_search and memory_get sitting in the same family. 'Optionally filtered by type or concept' implies a browsing use case but never states it or contrasts it with searching.

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