append_to_note

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states the tool appends markdown, implying additive behavior, and mentions section support and create_if_missing parameter. However, it does not explain the return format, whether appending is to the end or under a heading, or potential side effects like overwriting sections. It adds some context but lacks depth.

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 a single sentence with practical context, no filler or redundancy. It front-loads the core action and quickly conveys value. Every word 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?

Given the five parameters and no output schema, the description provides essential action context but omits information about return values or post-append behavior. It adequately distinguishes from siblings but leaves the agent guessing about what happens after invocation. Somewhat incomplete for a mutating tool with multiple parameters.

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 parameters well. The description repeats the action theme ('Append markdown') without adding new meaning to individual parameters beyond what the schema provides. The use-case context might help an agent decide to use create_if_missing, but it does not explain parameter details. 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?

The description uses a specific verb and resource: 'Append markdown to a note or section.' It distinguishes itself from sibling tools like create_note (which creates new notes) and apply_note_update (which might update more comprehensively) by focusing on appending. The use cases 'Inbox, logs, and incremental memory entries' further clarify its specific role.

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 explicitly suggests use cases: 'Useful for Inbox, logs, and incremental memory entries.' This provides context on when to use the tool. However, it does not explicitly state when not to use it or suggest alternatives, which would improve the score.

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