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

The description explicitly says '(READ-ONLY: mutations refused)' while the annotations declare readOnlyHint=false. It also describes mutating actions ('pin', 'release it with pinned=false'), directly contradicting the read-only claim. This is a serious inconsistency that could mislead an agent about whether the tool mutates data.

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 definition is a single front-loaded sentence with minimal waste. The core action and release option are stated immediately. The contradictory READ-ONLY parenthetical detracts from an otherwise efficient structure.

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?

This is a mutation tool with no output schema and only annotations covering some safety traits. The description omits what happens on success or failure, what galaxy mismatch refusal returns, and how the protection interacts with memory lifecycle operations. The contradictory read-only claim further undermines completeness.

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 id, galaxy, and pinned in detail. The description reinforces the pinned=false release behavior but adds no meaning beyond the schema, such as galaxy mismatch handling or UUID formatting. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 clearly states the specific operation: durably pinning a memory against decay, sweep compaction, and forgetting, or releasing it. The verb and resource are unambiguous. It does not explicitly distinguish this from siblings such as memory.update, which could also modify memory state, so it falls short of a 5.

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 implies when to use it by naming the condition 'critical memory' and explains that pinned=false releases the pin. However, it gives no explicit when-not guidance, prerequisites, or alternatives such as memory.update or memory.create, leaving usage context largely inferred.

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