Notes Update Note

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

The description adds no behavioral detail beyond the annotations. It does not disclose whether updates are partial or full replacement, what fields are affected, whether the operation requires permissions, or what happens to unspecified fields. With no such context and only boilerplate text, the description fails to carry its share of transparency burden.

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 text is short, but this is under-specification rather than conciseness. The single sentence contains only boilerplate about the tool being delegated and exposed, which does not earn 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?

For a mutation tool with five parameters, one required, and no usage or behavioral guidance, the description is completely inadequate. Even with an output schema present, the agent has no way to know what updating a note entails or how to invoke the tool correctly.

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%, and the description gives no explanation of note_id, title, body_html, folder_id, or tags. The description must compensate for the missing schema documentation but does not mention any parameter semantics at all.

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 merely restates the tool name: 'Delegated Apple domain tool notes_update_note exposed through Apple-Tools-MCP.' It gives no verb, resource semantics, or differentiation from sibling tools like notes_create_note, notes_append_to_note, or notes_move_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?

There is no guidance on when to use this tool versus alternatives. The title implies updating a note, but the description does not state what scenarios call for it or which sibling tools should be considered instead.

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