Append to a note (creates it if missing)

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

With no annotations, the description must cover behavioral traits. It discloses find-or-create behavior, plain text only, and default append-only on creation. However, it omits details on idempotency, error handling, or whether existing append-only locks are respected on subsequent calls.

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 two sentences with no filler. The first sentence captures the core action and find-or-create behavior; the second provides the use case and constraints. Every word serves a purpose.

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?

Given the tool's simplicity and lack of output schema, the description covers key aspects: purpose, find-or-create, usage pattern, and parameter constraints. It could mention response format or error scenarios, but is sufficient for an append operation.

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 100%, but the description adds value by explaining 'exact filename' with example, 'new entry' semantics for text, and the default behavior of append_only on creation. This enriches the schema's bare descriptions.

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 explicitly states 'Append text to the note' with a find-or-create behavior, distinguishing it from sibling tools like create_note or update_note. The logging use case is clearly articulated.

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 identifies the tool as a 'primitive for logging' with repeated calls for accumulating entries, providing clear context. However, it does not explicitly state when not to use it or list alternatives for other operations.

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