ima_append_note

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

With no annotations, the description must carry the full behavioral burden. It usefully clarifies that content is appended to the end rather than replacing the note, and that the input is Markdown, but it omits permissions, behavior on invalid or missing note_id, return value, and other mutation side effects—significant gaps for a write 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 a single front-loaded sentence with no wasted words. Every part of the sentence adds information about the action, target, and content type.

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?

There are no annotations, no output schema, and no parameter descriptions in the schema. The description is too sparse for a mutation tool: it leaves note-existence requirements, note_id acquisition, append behavior on errors, and return semantics unstated.

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 both parameters are required and undocumented in the schema. The description only implies that note_id identifies an existing note and content is Markdown; it does not explain where to obtain note_id, its format, or any content size/format constraints.

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 verb (追加/append) and resource (已有 IMA 笔记末尾/existing IMA note end), plus content type Markdown. It is clear enough to distinguish from reading or creating notes, though it does not explicitly contrast with siblings like ima_create_note or ima_insert_images_to_note.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The word '已有' implies the note must already exist, but the description does not tell the agent how to choose this over ima_create_note or what to do if the note is missing.

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