append_note

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: the failure mode when the target note is absent. It does not state where content is appended, whether the operation is idempotent, what permissions are required, or how errors surface.

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 short sentences with zero filler; the primary action is front-loaded and the constraint follows immediately. Every sentence earns its place.

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 described, and the key failure condition is covered. For a mutation tool with no annotations and 0% parameter coverage, though, the definition omits permissions, append position/ordering, and any note-creation guidance, leaving meaningful gaps.

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%, so both parameters (title, content) are undocumented in the schema and the description must compensate. The phrase 'append content to an existing note' loosely maps 'content' to the appended data and 'title' to the note identifier, but it never confirms this, so the mapping for the required 'title' parameter is left to inference.

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 ('an existing note'), making the core action unambiguous. It is clearly distinct from a hypothetical overwrite/create tool, though it never names siblings like save_note or append_response_to_note to sharpen the differentiation.

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?

'Fails if the note does not exist' implicitly signals that this is not for creating notes and that a creation tool is needed otherwise, which is useful routing context. However, it never explicitly says when to choose this over save_note or append_response_to_note, leaving the agent to infer the boundaries.

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