append_to_note

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Append content to an existing note' implies mutation (not read-only), it doesn't specify permissions needed, whether the operation is atomic, what happens if the note doesn't exist, or any rate limits. The description mentions use cases but lacks critical behavioral details for a mutation tool.

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?

The description is perfectly concise with two sentences that each earn their place. The first sentence states the core functionality, and the second provides valuable usage context. No wasted words, and the most important information (what the tool does) comes first.

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 mutation tool with no annotations and no output schema, the description provides adequate basic information about purpose and usage context. However, it lacks important details about error conditions, return values, and behavioral constraints that would be needed for complete understanding. The description does its job reasonably well given the tool's moderate complexity.

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%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in 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 description clearly states the action ('Append content') and target resource ('to an existing note'), making the purpose immediately understandable. It distinguishes from sibling tools like 'write_note' (which likely creates/overwrites) and 'read_note' (which only reads). However, it doesn't explicitly contrast with 'append_to_daily_note' which appears to be a more specific variant.

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 description provides clear context for when to use this tool ('Useful for adding entries to running logs, daily notes, or accumulating information'), giving practical scenarios. It implicitly suggests this is for incremental updates rather than full replacements. However, it doesn't explicitly state when NOT to use it or name specific alternatives like 'write_note' for overwriting.

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