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

With no annotations, the description carries the full burden and does substantial work: it discloses the default scope (durable recall, excludes working memory), the current-truth default versus include_superseded behavior, and the dependency of synthesis quality on retrieval. The only gap is that it never explicitly states the operation has no side effects/writes to memory, which is implied by 'runs durable recall... then composes' but not stated.

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?

Four dense sentences, each earning its place: purpose, pipeline and default scope, sibling routing, and the one flag worth flagging. The purpose is front-loaded in the first sentence, and the GBrain parity reference is a compact one-line contextual anchor rather than padding.

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?

Given an output schema exists (return values documented) and parameter coverage is 100%, the description covers everything an agent needs to invoke correctly: what it produces, its internal flow, default scoping, the retrieval prerequisite, sibling routing, and the superseded-data option. Nothing material is missing for a read-synthesis tool.

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 the schema already documents all six parameters, establishing the baseline of 3. The description re-emphasizes include_superseded in context ('Default sources are current truth; pass include_superseded=true') but adds no parameter meaning beyond what the schema provides.

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?

Opens with a specific verb+resource+output: 'Synthesized answer with citations and gap analysis' and describes the pipeline (durable recall → cited prose + explicit gaps). It explicitly differentiates from siblings by naming memory_recall and its complementary role, so an agent can distinguish this from memory_recall, memory_remember, and memory_assemble_context without opening schemas.

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?

Gives explicit routing guidance: for named-entity or competitor questions, call memory_recall with a short keyword anchor first, and prefer memory_think when prose + gaps are needed after recall hits or for open strategic questions. This is exactly the 'when vs. alternative' guidance the rubric demands, and it even notes the prerequisite retrieval step.

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