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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is fully covered without the text. The description adds that results are the user's saved facts/preferences and that limit is capped at 10, but says nothing about ordering, relevance ranking, or what happens when topic/project are empty.

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 tight sentences with the core behavior front-loaded and no redundant restatement of the name. The final sentence is slightly advisory but earns its place as usage direction.

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 and no parameter descriptions, the text should do more: it does not describe result structure, ordering, or the default/empty-filter behavior of a zero-required-parameter tool. It is adequate for a simple read but leaves real gaps for an agent calling it with only partial filters.

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 0% across three parameters, so the description must carry the meaning. It explains only `limit` (caps results, max 10, beyond the schema's default of 5), while `topic` and `project` are left unclarified — notably whether they can be combined, whether either is required, or what an empty value does.

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 gives a specific verb and resource: it returns saved 'key facts and preferences' tied to a topic or project, which is more precise than the title alone. However, it never distinguishes itself from the heavily overlapping siblings memory_search, memory_search_advanced, or memory_whats_up, so an agent cannot tell from the text why it should pick this one.

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 supplies a clear use context — check stated preferences before making a suggestion or writing on a topic — which is genuine when-to-use guidance. But it names no alternatives and gives no exclusions, so the agent must infer this versus memory_search or memory_get on its own.

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