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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description earns extra credit by disclosing that every unit carries a verbatim quote and instructing to cite rather than paraphrase, plus the cost attribute ('Free'). It omits output size/pagination behavior, keeping it below a 5.

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?

It is front-loaded with the definition, then the return contents, then usage and cost, in a dense, low-waste structure. Slightly long, but every clause (repeat counts, context, quote-citation instruction) adds selection or invocation value.

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 correctly compensates by detailing the returned categories and their counts, and it is complete for calling the tool. The only gap is that the required profile_id parameter and any empty-memory behavior are never described.

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?

The single parameter (profile_id) has 0% schema description coverage, so the description must carry the burden. It only implies profile scoping via 'this profile's writing' and never names or explains profile_id, though the parameter is a self-evident required UUID.

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 concrete verb (get/return) and resource ('Voice Brain') and then enumerates the exact payload: recurring ideas with repeat counts, stories, claims with context, frameworks, and topic counts. An agent can distinguish this read tool from the mutating memory siblings (add_to_memory, edit_memory, delete_memory) without opening schemas, though no sibling is named outright.

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 trigger conditions: 'Use it before drafting to build on established ideas and avoid repeating them' and 'to answer \'what have I written about X?\''. There are no when-not conditions or named alternatives (e.g. check_novelty, list_brains), so it stops short of full routing guidance.

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