cerebro_note

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

No annotations provided; description fills the gap by explaining the recording behavior and future retrieval via cerebro_recall. Simple write operation, transparent about purpose and content format.

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?

Concise and front-loaded: states purpose, gives examples, provides usage guidance. Every sentence adds value with no redundancy.

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 presence of output schema, description covers all needed aspects: purpose, usage context, parameter details, and integration with cerebro_recall. Sufficient for a simple note-taking 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?

Despite 0% schema description coverage, the description adds significant meaning: content is required (1-3 sentences), topic is optional short tag. This compensates for lack of schema descriptions.

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 records decisions, domain rules, or gotchas—the *why* behind code. It provides concrete examples and distinguishes from sibling tool cerebro_recall (retrieval).

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?

Explicitly advises when to use (record 'why'), includes formatting tips (1-3 sentences, optional topic). Does not explicitly state when not to use, but the context of siblings implies alternatives.

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