Apple Notes MCP

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

Annotations indicate this is a non-readonly, non-destructive, closed-world operation. The description adds that it 'overwrites' note body content, which aligns with annotations (non-readonly but non-destructive for the note itself). However, it doesn't disclose additional behavioral traits like authentication needs, rate limits, or what 'overwrite' entails for existing content.

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 description is a single, efficient sentence that front-loads the key action ('Overwrite a note body') and specifies the outcome ('professional action plan with headings, lists, timestamp'). No wasted words 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?

Given the tool has an output schema (which handles return values), annotations cover basic safety, and it's a mutation tool with 3 parameters, the description is minimally adequate. However, it lacks details on parameter usage, error conditions, or how the template is applied, leaving gaps in context for effective use.

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 schema provides no parameter descriptions. The tool description mentions 'note body' but doesn't explain the three parameters (id, title, context) or their roles in applying the template. Baseline is 3 since schema coverage is low, but the description doesn't compensate by clarifying parameter meanings.

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 clearly states the verb ('Overwrite') and resource ('note body') with specific content ('professional action plan with headings, lists, timestamp'). It distinguishes from generic update tools but doesn't explicitly differentiate from siblings like 'notes.apply_format' or 'notes.update'.

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 this tool versus alternatives like 'notes.update', 'notes.apply_format', or 'notes.append_text'. The description implies it's for transforming notes into action plans but doesn't specify prerequisites, exclusions, or comparison with sibling tools.

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