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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context such as default pagination or scope limitations, but it also does not contradict the annotations.

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?

The description is a single concise sentence that front-loads the core action and then lists filters. It contains no unnecessary words, though it could be slightly more precise with the parameter names.

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 an output schema present and all parameters documented in the input schema, the description does not need to explain return values or parameter formats. The only notable gap is the 'tags' vs 'exclude_tags' mismatch, but overall the information needed to call the tool correctly is available from the schema and annotations.

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 100%, so the schema already documents all four parameters. However, the description's filter list says 'tags' while the actual parameter is 'exclude_tags', which is a misleading shorthand that could cause an agent to pass an invalid parameter name. This inaccuracy outweighs the minimal value added by summarizing the filters.

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 ('List') and resource ('memories') and mentions the available filters, making the tool's function immediately clear. The action 'list' is distinct from siblings like memory.read, memory.search, and memory.hybrid_recall, so an agent can tell them apart.

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 description says the tool is 'for inventory and discovery', which implies a browsing context but does not explicitly state when to use it over alternatives like memory.search. It provides no exclusions or comparisons to sibling tools, leaving the decision to inference.

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