Notes Append To Note

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

Annotations exist (openWorldHint=false, idempotentHint=false, destructiveHint=false), so the safety profile is partly covered, but the description adds zero behavioral context: no mention that appending modifies an existing note in place, what happens with a nonexistent note_id, or any side effects. It contributes no behavioral information beyond what the name implies.

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 single sentence is short but earns no place: it repeats the tool name and references the MCP framework instead of conveying function. This is under-specification masquerading as conciseness, not efficient writing.

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?

The tool is simple (2 required params, output schema present), which lowers the completeness burden, but the description still fails to explain the core operation, the precondition that a target note must exist, or the relationship to sibling note-mutation tools. An agent would have to guess the behavior from the name alone.

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 carries the burden of explaining note_id and body — and it says nothing about either parameter. The names are mildly self-explanatory (an ID and a text body), but the description does not compensate for the complete lack of schema documentation, such as format expectations for note_id.

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 is a tautology: it quotes the tool name verbatim ('notes_append_to_note') and adds only meta-framework noise ('Delegated Apple domain tool', 'exposed through Apple-Tools-MCP'). It never states the actual function — appending body text to an existing note. The only purpose hint comes from the name itself, not the description.

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 gives no guidance on when to use this tool versus the dozens of sibling notes tools (notes_create_note, notes_update_note, notes_delete_note). Nothing distinguishes when appending is the right operation versus updating or creating a note. No exclusion criteria or alternative routing is provided.

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