brain_write

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly mentions the overwrite behavior and the auto-reindex side effect, which is useful. However, it does not disclose permissions, irreversibility consequences, or failure modes.

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: two short sentences with no filler. 'Create or overwrite a vault file' front-loads the core purpose, and 'Auto-reindexes' adds a valuable behavioral note without extra words.

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?

The tool is simple with only two parameters, and an output schema is present, so return-value explanation is unnecessary. Still, the description lacks parameter-level detail and sibling differentiation, leaving the agent to infer important invocation details.

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 description coverage is 0%, and the description does not explain the path or content parameters beyond the generic 'vault file' context. The agent can infer that path likely identifies a file and content is the file body, but the description adds little meaningful parameter semantics.

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 specific action and resource: 'Create or overwrite a vault file.' This clearly distinguishes it from sibling read, search, list, and append tools, and the name brain_write reinforces the purpose.

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 implies when to use the tool: when creating or overwriting a file. However, it gives no explicit guidance about when not to use it or which sibling tool should be preferred for alternative operations, such as brain_append for appending content.

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