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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false; the description goes further by naming the required resources:read permission, the workspace-wide grant needed for unlinked notes, the requestId retry mechanism, and permission enforcement across workspace/project/account. The only weak spot is a sentence about item_update versioning that is tangential to this tool and slightly muddies the write path.

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?

Front-loaded with the core action and immediately followed by the sibling routing rules, so the most important content comes first. It is dense and mostly earns its length, though the trailing sentence about item updates requiring a version from get_tasks/get_items/get_workspace belongs to a different tool and dilutes focus.

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 5-parameter mutation tool with no output schema and sparse schema descriptions, the description covers visibility semantics, permission prerequisites, idempotency, and alternatives. It stops short of describing the returned object or duplicate-title behavior, but an agent has enough to invoke it correctly.

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 only 20% (just targetId), but the description compensates by explaining title/body as Markdown content, projectId and optional task linking (targetId), and the requestId uniqueness/retry contract. It does not add format details like UUID patterns or max lengths, which the schema already supplies.

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 and resource ('Write an editable library note in Binder's Resources') plus the content types it is meant for (brief, plan, instructions, reusable reference). It explicitly distinguishes itself from the two nearest siblings: note_append (permanent comments) and file attachments/exports.

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?

Gives explicit routing rules: use note_append for permanent project/task comments such as updates and decisions, and keep original attachments and exports as files. It also states the project/task linking conditions and what happens without a project (workspace-wide visibility requiring a workspace-wide grant).

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