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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the retrieval mode ('hybrid semantic, BM25, and associative retrieval'), which offers some insight into how it behaves, but it does not disclose other behavioral traits such as auth needs, rate limits, or side effects beyond what annotations and parameter descriptions already do. The description neither contradicts nor substantially exceeds annotation coverage, so a 3 is appropriate.

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 sentence that is concise and front-loaded with the core purpose and retrieval approach. There is no filler or repetition, and every word contributes value. It is appropriately sized for a search tool with a detailed schema.

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?

The tool is complex with nine parameters and an output schema, but the description is minimal. It covers the broad purpose but does not explain typical use cases, how it differs from sibling tools, or when to set various filters. The presence of an output schema and comprehensive parameter descriptions reduces the burden, yet the lack of usage context and sibling differentiation leaves gaps. A score of 3 reflects that it is adequate but not complete.

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 all nine parameters are documented in the schema. The description does not add additional parameter semantics; it only mentions retrieval methods that loosely relate to the query parameter but does not clarify syntax, defaults, or inter-parameter relationships beyond the schema. With high schema coverage, the baseline is 3, and the description does not elevate it.

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 states a clear action ('search and recall memories') with a specific scope ('across galaxies') and method ('hybrid semantic, BM25, and associative retrieval'). It is more specific than the title, but it does not explicitly differentiate from the sibling tool memory.hybrid_recall, which is likely a similar retrieval function. Thus, it is clear but not fully distinguishing.

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?

No guidance is provided on when to use this tool versus alternatives like memory.hybrid_recall, memory.list, or memory.read. It does not state prerequisites, exclusions, or conditions that would route an agent to this tool over its siblings. The description is purely functional with no decision-making context.

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