Append text to the end of a specified note in a ZenNotes vault using the note's path and the text to add. Extend existing notes without overwriting content.
Ajoute du texte a la fin d'une note.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| text | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description alone carries the burden. It mentions appending text but does not clarify side effects (e.g., whether the note must already exist, if it modifies in place, or if it is non-destructive).
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 a single, concise sentence that directly conveys the tool's purpose without unnecessary verbosity.
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 description lacks information about return values, error handling, or prerequisites. It is minimal and leaves out context that an agent might need to use the tool effectively.
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 schema has no descriptions for 'path' or 'text', and the description does not elaborate on their meaning. The parameter names are self-explanatory, but the description provides no additional context, so coverage is minimal.
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 clearly states the action: appending text to the end of a note. It is specific to the tool's name and distinguishes it from prepend or write operations.
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 explicitly state when to use this tool versus alternatives like prepend_to_note or write_note. The intent is implied by the verb 'append' but not made explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.