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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, all consistent with a recall operation. The description adds context the annotations do not carry: the owner-gated auth requirement (handle+secret) and the response envelope {ok, bank, result}. It does not cover paging or truncation behavior, but it clearly exceeds the annotation baseline.

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?

Very short and front-loaded with the verb and resource, with auth and return shape following. The bracketed '[learns]' token and parenthetical '(hindsight)' are low-value noise, but overall there is little waste.

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 7-parameter, 2-required tool with no output schema, the description covers purpose, auth, and a bare return envelope, which is the minimum viable. It omits what the result contents actually look like, how many memories are returned, and any relationship to the other memory tools, leaving real gaps for an agent operating in this sibling cluster.

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 seven parameters are already documented in the schema, including bank, tags, query, and max_tokens. The description restates the query argument and implies the personal vs shared bank notion but adds no format, syntax, or default detail beyond the schema. Baseline 3 is appropriate.

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 (Recall) and resource (memories) scoped to the 'learning memory bank (hindsight)' with a query argument. However, it never distinguishes itself from near-identical siblings such as recall_memories, search_memory, and list_memory, so an agent cannot tell which recall variant to pick from the description alone. The cryptic '[learns]' prefix adds no clarity.

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 when-to-use guidance and no named alternatives, despite a crowded sibling set of memory-retrieval tools (recall_memories, search_memory, search_memory_facts, list_memory). The only condition given is the owner-gating prerequisite (handle+secret), which is an auth note rather than selection guidance.

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