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

With no annotations, the description carries the full burden and largely succeeds: it discloses that durable recall's default scope excludes working memory, that default sources are current truth only, and that synthesis quality depends on retrieval. It does not cover auth/permission requirements, cost or latency implications, or idempotency, so it is not fully complete.

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?

Purpose is front-loaded before the workflow and parameter guidance, and the structure is easy to scan. There is mild redundancy with the schema's descriptions of include_superseded and as_of, and jargon like 'GBrain think parity' adds little for an agent.

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?

An output schema exists, so return values need not be explained, and the description still covers the retrieval-then-synthesis workflow, scope defaults, and temporal options for a 7-parameter tool. It is slightly thin on operational concerns (permissions, expense) but complete enough to invoke 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 100%, so all seven parameters are already documented. The description's mention of include_superseded and as_of largely restates the schema's own text ('include retired facts', 'point-in-time grounding') rather than adding new semantics, so the 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?

The opening line states a specific verb+resource+output ('Synthesized answer with citations and gap analysis') and immediately scopes it ('runs durable recall... then composes a cited prose answer plus explicit gaps'). It also differentiates itself from the sibling memory_recall by naming it and the condition that selects it, so an agent can distinguish the two without opening either schema.

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?

Explicit routing guidance: 'call memory_recall with a short keyword anchor first' for named-entity or competitor questions, and 'prefer memory_think when you need prose + gaps after recall surfaced hits, or for open strategic questions.' This names the alternative and the exact conditions for choosing each.

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