read_memory

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

With no annotations, the description carries the behavioral burden and discloses meaningful traits: hybrid search mechanics, rank fusion, importance/recency re-ranking, and the honesty-floor message when nothing relevant is found. It does not explicitly state read-only behavior or permission requirements, but the core search behavior is well covered.

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?

Two tightly written sentences front-load the search mechanics and scope before moving to usage guidance and the honesty-floor behavior. Every sentence carries useful information with no wasted wording.

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 description covers purpose, usage, and behavior well, and an output schema exists so return values need not be described. However, with 0% schema description coverage for three parameters, it remains incomplete regarding how to use query, limit, and domain correctly.

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 compensate for three undocumented parameters. It barely implies that the query should be topic-specific but says nothing about limit or domain, leaving most parameter semantics unexplained.

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 specific operation — hybrid search over the trail — and clarifies it is for topic-specific history rather than current state. It distinguishes itself from pins/wiki, but it does not differentiate from the sibling search_memory, which is likely the closest alternative.

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 gives explicit usage guidance: use for topic-specific HISTORY, not for current state (pins/wiki). This is clear context and an exclusion, but it omits the direct alternative for historical memory search, such as search_memory.

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