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

Annotations establish it is a write (readOnlyHint=false) and not idempotent (idempotentHint=false). The description adds curation behavior guidance ('Keep entries concise and factual', exclude generic K8s knowledge), which goes beyond the annotations. It does not disclose what happens on duplicate saves or persistence/scope lifetime, leaving a minor gap on the non-idempotent trait.

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?

Front-loaded with the core action, followed by a dense but purposeful trigger list. Every sentence carries a rule, though the trigger enumeration is longer than strictly necessary and could be tightened into fewer clauses.

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?

A mutation tool with 2 fully documented params and no output schema; the description covers what to save, when, what to exclude, and how to set the scope flag. Remaining gaps (duplicate handling, whether saved memories are retrievable/editable, retention) are secondary for correct invocation.

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?

With 100% schema description coverage the baseline is 3, and the description adds concrete disambiguation for cluster_specific ('Set cluster_specific=false for personal or organization-wide facts') plus content-quality guidance for the content field, slightly exceeding what the schema alone conveys.

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: 'Save an important fact, decision, or preference to long-term memory for future conversations.' The scope (durable cross-conversation memory of facts/decisions/preferences) is unambiguous and clearly distinct from siblings like search_memories or ask_question.

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?

Gives explicit positive triggers ('ALWAYS use this when the user shares personal details', explicit remember requests, significant decisions, resolved root causes, discovered topology) and explicit exclusions ('Do not save generic Kubernetes knowledge'), which is about as complete as when-to-use guidance gets.

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