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

Annotations already declare the operation read-only, idempotent, closed-world and non-destructive, so the bar is lower. The description adds one genuinely useful behavioral constraint, that limit is capped at 10, but it says nothing about what happens when topic and project are both empty, or how results are ranked.

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?

Three short sentences, front-loaded with what is returned, then the limit cap, then the usage cue. No filler and no repetition of the title.

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?

There is no output schema, so the description does the work of saying what comes back, which it does. For a tool with three optional zero-documented parameters, however, it leaves the empty-input behavior and the topic-versus-project relationship unexplained.

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 0%, so the description has to carry the parameter load, and it only partly does. It explains the role of limit and its maximum of 10 and gestures at topic and project, but never clarifies how the two filters combine, what the defaults mean, or whether an empty string returns everything.

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: returns saved key facts and preferences related to a topic or project. That separates it from obvious storage tools like memory_store, but it never distinguishes it from retrieval siblings such as memory_search or memory_get, so an agent cannot tell which retrieval to pick from purpose alone.

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 a concrete usage scenario: check the user's stated preferences before making a suggestion or writing something on that topic. That is clear context, but it offers no exclusions or named alternatives, so nothing tells the agent when memory_search would be the better call.

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