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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the trailing 'Read-only' largely repeats it. The genuinely additive behavioral fact is that matching is keyword/exact rather than semantic, but return format, ordering and pagination behavior are unstated.

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 with zero filler; the core purpose is front-loaded and the usage trigger and safety note follow in order of relevance. Nothing could be removed without losing signal.

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?

For a simple two-parameter read tool with annotations carrying the safety profile, the description is adequate to invoke it. It is incomplete on the routing question (why this over 'search' or 'recall_memories') and gives no hint of what a result looks like or how it is ordered.

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% — 'query' (search terms) and 'limit' (max results, default 10, range 1-50) are fully documented in the schema. The description adds nothing about syntax, phrase handling, or case sensitivity, so baseline 3 applies.

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 ('Keyword search over the user's saved memories') and adds the mechanism (keyword/exact-match), which is more informative than the title. However, it never distinguishes itself from the closely named siblings 'search' and 'recall_memories', so the agent cannot fully disambiguate without inspecting schemas.

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?

'Use when the user gives exact words or names' gives a concrete, actionable trigger condition that separates keyword lookup from fuzzy/semantic recall. It stops short of naming the alternative tools (recall_memories, search) or stating when NOT to use it, so routing remains partly inferential.

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