write_note

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

The description reveals the destructive nature ('Overwrite') but does not mention other side effects such as creating parent directories, updating metadata, or handling of existing content beyond replacement. With no annotations, more detail would improve transparency.

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 two sentences: one stating the function, one providing usage guidance. No wasted 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, and the description covers the primary purpose and usage condition. It does not mention error cases or return values, but those are likely covered by the output schema (not shown) and the simplicity of the operation.

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?

The parameters are fully described in the schema (path as vault-relative path, content as complete note content), so the description adds little beyond restating that content must be complete. Baseline of 3 is appropriate.

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 action ('Overwrite or create'), the target ('Markdown note'), and the input ('complete content'). It distinguishes itself from append_note by specifying the caller already has complete content.

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?

Provides an explicit condition for use: 'Use this when the caller already has the complete .md content.' This tells the agent exactly when to select this tool over alternatives like append_note or create_note.

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