Load the owner's identity and standing context

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

Annotations already declare this is a safe, idempotent, closed read, so the description is free to add behavioral meaning beyond safety: the bundle is a persona/working-context payload meant to be adopted, and passing `topic` changes the payload composition. It doesn't state format, size, or latency of the full bundle, but the added context is substantive.

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?

Front-loaded with the imperative invocation rule, then the return contents, then the optional narrowing parameter. Four tight sentences with no filler.

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?

With no output schema, the description carries the burden of describing what comes back, and it enumerates the payload well (identity, preferences, feedback rules, projects, recent activity). It omits payload size/format expectations, which is the only real gap for a bundle of this scope.

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 coverage is 100% and the schema already says "Omit for the full bundle," so 3 would be the baseline. The description earns above baseline by explaining the tradeoff the parameter actually controls — a smaller bundle containing only the memory notes that apply — which clarifies the filtering effect on returned content.

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 (Returns) and enumerates the exact resource contents: owner identity, preferences and feedback rules, projects, recent activity. This is distinctly different from read/search siblings like brain_search or brain_read, so an agent can route to it 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?

"Call this FIRST in every conversation" gives a clear, strong usage condition, and the description explains when to narrow with `topic`. It stops short of naming alternatives or a when-not condition (e.g., what to use for later queries in the same conversation), so it isn't fully explicit about the sibling choice.

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