append_to_note

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

Annotations already declare this is mutating (readOnlyHint false) and non-destructive; the description adds the behavior that the .md extension is appended automatically. It does not describe failure behavior when the note is missing or how newlines are handled, but this is not contradictory to annotations.

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 short sentences, with the core action first and the extension detail second. No filler or redundancy.

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 two-parameter mutation with no output schema, the description covers the main purpose and the key .md extension behavior. Gaps remain around error handling (missing note) and exact append formatting, so it is minimally viable but not thorough.

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 carry the burden for both params. It implicitly associates path with the note file (including automatic .md extension) and content with the text to append, but offers no details on path format, trailing newlines, or content constraints.

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?

States a clear action ('Append text') and target ('an existing note'), and specifies position ('to the end'), which disambiguates from prepend_to_note and create_note. The mention of automatic .md extension adds useful file-handling detail.

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?

No explicit when-to-use guidance or named alternatives are given. The wording 'existing note' and 'to the end' implies not for creating new notes or prepending, but an agent must infer this rather than being told.

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