Append Note

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

Annotations are minimal (only title). Description implies mutation but does not disclose whether the operation is idempotent, error behaviors, or permission requirements.

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?

Single sentence with no extraneous words. Information is front-loaded.

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 0% schema description coverage and multiple parameters, the description is too brief. It does not explain what happens when both title and note_id are provided, or the role of account. An output schema exists but does not excuse missing parameter context.

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?

The description adds meaning by explaining that note identification can be via stable ID or title, which is not fully detailed in the schema. However, it does not explain the 'account' parameter or the 'text' parameter beyond the schema.

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?

Clearly states verb 'Append text', resource 'note', and identification method 'by stable id or title'. Distinguishes from sibling tools like notes_create, notes_read, notes_delete.

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 guidance on when to use append versus other tools. Does not mention alternatives or prerequisites like ensuring the note exists.

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