brain_append

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

With no annotations present, the description carries the full burden of behavioral disclosure. It adds one useful behavior, 'Auto-reindexes,' but does not explain whether the file must already exist, whether the operation is irreversible, or what side effects occur beyond reindexing. This is a meaningful gap for a mutating tool.

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 extremely concise, with only two short sentences. The core operation is front-loaded first, and the second sentence adds a relevant behavioral detail. There is no wasted wording.

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 2-parameter tool this is simple, but without annotations and with no sibling differentiation or parameter guidance, the description is incomplete. An agent can guess how to call it, but not confidently understand edge cases like missing files, reindex behavior, or when to prefer brain_write.

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?

Input schema description coverage is 0%, so the description must compensate. It does not explain the expected format of 'path' or 'content,' nor does it clarify relative versus absolute vault paths. The parameter names are somewhat self-explanatory, but the description adds little semantic value beyond what the schema already exposes.

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 the exact operation: 'Append to a vault file.' The verb and resource are specific, and 'append' inherently distinguishes it from sibling tools like brain_write. It gives an agent enough clarity to understand what this tool does.

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 does not explain when to choose this tool over related alternatives such as brain_write. 'Append' implies a use case, but there is no explicit guidance about when appending is appropriate versus overwriting, creating, or logging.

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