append_file

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

No annotations are present, so the description carries the full burden. It discloses that appending occurs, `updated` is bumped, and the note is created if missing, which is useful behavioral context. However, it does not mention permissions, failure modes, or idempotency, leaving some gaps for a mutation 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?

Two sentences with no fluff. Each sentence carries meaningful information, and the 'WRITE' category and 'appends' action are front-loaded for quick scanning.

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 simple two-parameter append operation with an output schema, this description covers the core behavior and the key edge case (create-if-missing). It does not discuss path formats or error handling, but those are minor for this tool. The 'bumps updated' detail adds useful context.

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 input schema has 0% description coverage, so the description must compensate. It implies 'content' is the data to append and 'path' identifies the note, but it does not explicitly map either parameter. Since both names are self-explanatory, this is adequate but not thorough.

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?

States a specific verb ('appends') and resource ('a note'), and clarifies it also creates the note when missing. However, it does not explicitly distinguish itself from the sibling 'write_file' though the word 'appends' implies the difference.

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 appending to a note and notes the create-when-missing behavior, but does not explicitly state when to choose it over alternatives like write_file. No clear when/when-not guidance is provided.

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