append_to_note

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

With no annotations provided, the description carries the transparency burden. It discloses that the operation is non-destructive ('leaving existing content untouched') and that checklist formatting is transformed ('- [ ] item' becomes a real checklist item). This covers key behavioral traits for a simple append operation.

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 concise sentences. The first sentence front-loads the core action and scope, the second adds a meaningful example of special behavior. No filler or repetition.

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 low-complexity tool with two params and no output schema, the description adequately covers its purpose, non-destructive nature, and one notable edge case. It omits error behaviors (e.g., note not found) but these are not critical given the straightforward action.

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 100%, with both parameters already documented ('Note name (exact) or note id' and 'Markdown to append'). The description adds no new parameter-level semantics; the checklist behavior applies to the markdown parameter but is more behavioral than parameter-specific, so baseline 3 is appropriate.

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?

Description clearly states the verb 'Append', the resource 'note', and the specific scope 'to the end'. It also distinguishes itself from replace-style tools by noting 'leaving existing content untouched', and adds the unique behavior of converting checklist syntax to real checklist items.

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?

The phrase 'leaving existing content untouched' implicitly contrasts with replace_note_content, but the description does not explicitly name alternatives or provide when-not guidance. It gives clear context for its intended use case without explicit exclusions.

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