ima_add_note_to_knowledge

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

With no annotations, the description carries the full burden. '关联添加' hints that this creates a link/reference rather than copying the note's content, which is useful, but it says nothing about permissions, idempotency (what happens if the note is already linked), or whether the source note itself is modified.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. However, that brevity reflects under-specification rather than efficiency, since key operational detail is simply absent.

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?

A four-parameter mutation tool with no annotations, no output schema, and zero documented parameters needs considerably more than one sentence. Nothing covers the required title, the optional folder, error/duplicate behavior, or how to find a valid knowledge base.

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% across four parameters, and the description explains none of them. The mandatory 'title' parameter is especially puzzling for an operation on an existing note, and 'folder_id' is never mentioned, so an agent cannot reason about them from the description.

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 sentence states a specific verb (add/link, 关联添加) and names both the resource being moved (an existing IMA note) and the target (an IMA knowledge base). This distinguishes it reasonably from ima_upload_file_to_knowledge (files vs. existing notes), though it does not explicitly name that sibling to sharpen the contrast.

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 statement of when to use this versus alternatives, and notably no reference to ima_get_addable_knowledge_bases, which is the obvious prerequisite for obtaining a valid knowledge_base_id. Preconditions and exclusion cases are left entirely to inference.

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