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

The readOnlyHint annotation already establishes the operation as non-mutating, and the description's 'Read' / 'list keys' wording is consistent with it. The description adds useful behavioral detail by specifying that omitting a key triggers listing and that a prefix can narrow the keys returned. It does not describe return format or missing-key behavior, but those are not essential for a simple read-only tool.

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 description is a single sentence with no wasted words. The primary behavior is front-loaded, and the parenthetical 'optionally by prefix' elegantly captures the only parameter nuance.

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 low-complexity tool with two optional string parameters, a read-only annotation, and no output schema. The description sufficiently covers both invocation modes and parameter semantics for an agent to call the tool correctly. It does not describe return-value shape or missing-key behavior, but those are not necessary for correct selection and 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?

Schema description coverage is 0%, so the description must carry the parameter documentation. It explains that key is the value to read and prefix is an optional filter for listing keys, and it clarifies the conditional relationship between them. It does not formally state that both are optional, but 'optionally by prefix' and the empty required list make that clear.

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 uses specific verbs 'Read' and 'list keys' and identifies the resource as a memory key, clearly conveying the two operational modes. It distinguishes itself from writing tools by emphasizing read/list behavior, though it does not explicitly name sibling tools for contrast.

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 gives a clear condition for list mode ('when no key is given') and notes that prefix is optional, which helps an agent choose parameters. However, it does not explicitly explain when to prefer recall over sibling memory tools like remember or forget, leaving some tool-selection guidance to inference.

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