Append Note Section

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

With no annotations, the description carries the full disclosure burden. It does add genuine behavioral detail beyond the schema (the blank-line separator rule, with the empty-note and trailing-separator exceptions), but it omits whether the note must exist, whether the change is reversible, permission requirements, and the mutation semantics relative to update_note.

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 lean sentences, front-loaded with the core action; the separator rule follows as the key edge case. Nothing is wasted and nothing important is buried.

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?

An output schema exists, so return values need not be explained, and the description covers the main behavioral quirk. What remains thin is the mutation context (auth, failure when the note is missing), but for a simple append operation the coverage is nearly sufficient.

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 coverage is 0%, so the description must compensate. It does clarify that content is the text appended to the end of the body, but says nothing about note_id (format, where it comes from) or how content is merged. Partial compensation for a small two-parameter tool.

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?

Specific verb + resource + scope: "Append content to the end of a note's body" tells the agent exactly what is modified and where. The phrase "without needing to know or resend its existing content" implicitly separates it from update_note/update_note_section, but no sibling is named explicitly, so differentiation is inferential rather than stated.

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?

Usage is implied: the append-without-resending framing suggests this over a full update when you only want to add text. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as the note existing, and no named alternative among the many sibling note tools.

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