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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the word 'versioned', which meaningfully refines the destructive hint by implying prior values are retained rather than lost, plus the persistence guarantee — real context beyond the annotations, though it doesn't state permissions or return behavior.

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?

A single front-loaded sentence with no filler; the verb-and-resource core comes first and the qualifying details ('persistent home', 'versioned') follow compactly. Every word earns its place.

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 mutation tool with no output schema, the description adequately covers what gets stored, where, and that storage is versioned, while annotations carry the destructive/idempotent profile and the schema covers all three parameters. It never hints at what the call returns (e.g. a version identifier), which is the only visible gap.

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 key format constraints, the free-form value type and the api_key auth note are all documented in the schema. The description's 'any JSON value under a key' merely restates that, adding no syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 (Store) and resource (any JSON value under a key) with scope ('in your persistent home'), which cleanly separates it from the get_memory / delete_memory siblings in the CRUD trio. It stops short of naming those siblings explicitly, so it falls just under 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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named even though add_note, house_put and similar storage siblings exist. The agent must infer purpose purely from the tool name and the phrase 'persistent home'.

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