append_to_note_tool

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the operation avoids rewriting the whole file and that create=True creates a missing note, but it does not explain mutation effects, error handling, concurrency behavior, or how expected_revision is used.

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 short and front-loaded with the core purpose. The parameter notes are compact and useful, though slightly telegraphic. Every sentence earns its place, but the structure could be clearer.

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 simple append operation, the description covers the main behavior and two important parametersfake. However, it omits explanation of expected_revision and vault, and since there are no annotations, an agent may lack sufficient context for edge cases. An output schema exists, so return values need not be described.

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 the description must compensate. It explains 'section' and 'create' but leaves path, vault, content, and especially expected_revision undocumented beyond their names. This is a significant gap for a six-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?

The description uses a specific verb and resource: 'Append content to a note'. It also distinguishes itself from a full rewrite by stating 'without reading and rewriting the whole file', which differentiates it from write_note_tool and patch_note_tool.

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 implies when to use the tool ('without reading and rewriting the whole file') and explains the create flag behavior, but it does not explicitly name alternatives or state when not to use this tool. Usage context is clear but exclusions are missing.

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