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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral context: omitting the key lists all keys, and the tool is scoped to a per-identifier memory space. It does not contradict annotations and provides useful supplementary details.

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 sentences, each earning its place: the first states the core functionality, the second gives use cases, and the third explains scoping and related tools. There is no fluff or repetition, and the most important information is front-loaded.

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 tool with one optional parameter and no output schema, the description is thorough. It covers the purpose, usage scenarios, scoping, and the relationship to sibling tools (remember, forget), providing everything an agent needs to decide when and how to invoke it.

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 coverage is 100% with the key parameter already described as 'Memory key to retrieve (omit to list all keys).' The description adds semantic meaning by explaining the key references a value saved via 'remember' and by giving concrete examples (user's target ticker, address, research notes), which helps an agent understand what kind of data to expect.

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 opens with a specific and clear action: 'Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).' It names the resource (saved memory) and the two modes of operation, and it explicitly distinguishes itself from siblings by referencing 'remember' and 'forget' as complementary tools.

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?

The description explicitly states when to use the tool: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It also provides clear alternatives and relationships: 'Pair with remember to save, forget to delete.' The scoping note ('Scoped to your identifier (anonymous IP, BYO key hash, or account ID)') helps the agent understand applicability.

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