brain_supersede

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

Describes closing old edges and writing a supersedes edge, providing some behavioral context. However, without annotations, it misses disclosure on destructiveness, side effects, or whether the old node remains. No mention of permissions or rate limits.

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?

Single, well-structured sentence that front-loads the key action and consequence. No unnecessary words; every part earns its place.

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?

Covers core behavior for a graph update tool, but lacks return value information, reversibility, and whether the operation generates a new node ID. Adequate but with gaps given no output schema or annotations.

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 description adds context by explaining the role of each parameter in the supersede operation, e.g., 'old_node_id' and 'new_content' as updated content. 'new_label' defaults to old label, which is helpful.

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?

Clearly states the verb 'Replace' and resource 'outdated node', explaining the process of closing old edges and writing a supersedes edge to preserve temporal integrity. This distinguishes it from sibling tools like brain_write or brain_forget.

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?

Implies usage for updating content while maintaining history, but does not explicitly state when not to use or mention alternatives among siblings. Lacks guidance on prerequisites or context.

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