Brainstorm with memory

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

Annotations show readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds value by explaining that the tool pulls prior thinking, promotes on reuse, and returns a brainstorm pack. There is no contradiction with annotations. It does not mention potential side effects beyond promotion, but for a brainstorming loader, the transparency is good.

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?

The description is well-structured with separate paragraphs for purpose, usage, and flow. It front-loads the core functionality. While slightly verbose, every sentence contributes useful information. It could be trimmed slightly but remains efficient.

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 tool with one parameter and no output schema, the description is complete. It explains the return value (brainstorm pack), the workflow (load, brainstorm, save), and the context (shared memory). It also references sibling tools appropriately, making the tool fully understandable in its ecosystem.

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?

Only one parameter (topic) with full schema description coverage (100%). The description repeats the meaning ('what you're brainstorming about') but adds no new syntax or constraints beyond the schema. Baseline 3 is appropriate as the schema already provides the semantics sufficiently.

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 clearly states the tool loads prior context for brainstorming on a topic using shared memory. It distinguishes itself by emphasizing that it pulls past brainstorms and related discussions, and it explicitly says when to call it proactively. The purpose is specific and actionable.

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?

The description provides explicit guidance on when to use it: when the user wants to brainstorm, ideate, think through, or explore options on something that may have history. It also notes what it does not do (replace brainstorming ability) and gives a follow-up action (capture with mindmap_capture). It even mentions the 'promote-on-reuse' behavior.

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