append_to_note

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

No annotations are provided, so the description carries full behavioral disclosure. It states it appends plain text but fails to disclose important traits: behavior when note does not exist, handling of identifier ambiguity (multiple notes with same title), impact on rich text notes, or if it creates the note if missing. Error handling is not detailed.

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?

Description is concise at two sentences plus bullet-style Args and Returns. It is front-loaded with the main action. Every sentence provides value, though the Args section could be integrated for brevity. Overall efficient and clear.

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?

An output schema exists, so return value details are not needed. However, given the tool's simplicity and lack of annotations, the description omits critical behavioral context: what happens if identifier matches multiple notes, if note not found, or if body is not plain text. It is minimally viable but leaves gaps.

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 has two required string parameters with 0% description coverage. The description adds meaning: 'identifier' can be a note id or title, and 'body' is plain text. This clarifies usage beyond the schema. However, it could specify the expected format for identifier (e.g., UUID) or constraints on body length.

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?

Description clearly states 'Append plain text to a note by id or title.' This specifies a concrete verb 'append' and resource 'note,' with the method 'by id or title.' It distinguishes from sibling tools like 'update_note' (which likely modifies or replaces content) and 'create_note' (which creates a new note).

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 usage for appending text, but it does not explicitly state when to use this tool over alternatives like 'update_note' (which might replace content) or 'create_note.' No guidance on prerequisites (e.g., note must exist) or exclusion criteria. Usage is implied but not clarified.

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