Apple Notes MCP

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

Annotations indicate this is a non-destructive, non-read-only mutation (readOnlyHint: false, destructiveHint: false), which the description aligns with by implying modification ('Append'). However, the description adds minimal behavioral context beyond annotations—it doesn't specify effects like whether the link is added at a specific position, if duplicates are allowed, or any rate limits. No contradiction with annotations exists.

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 directly states the tool's function without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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's moderate complexity (3 parameters, mutation operation) and the presence of an output schema (which reduces need to describe returns), the description is minimally adequate. However, it lacks details on parameter usage, behavioral nuances, and sibling differentiation, leaving gaps that could hinder optimal tool selection and invocation.

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?

With 0% schema description coverage, the schema provides no parameter details, but the description also adds no information about parameters like 'id', 'url', or 'text'. It implies parameters are needed for appending a link but doesn't explain their roles or formats. Baseline is 3 due to the schema's lack of descriptions, but the description fails to compensate meaningfully.

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 action ('Append') and resource ('hyperlink to a note'), making the purpose immediately understandable. It distinguishes from siblings like 'notes.append_text' by specifying hyperlinks rather than general text, though it doesn't explicitly contrast with all similar tools like 'notes.update' which might also modify notes.

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 provides no guidance on when to use this tool versus alternatives such as 'notes.append_text' for plain text or 'notes.update' for broader modifications. It lacks context about prerequisites, exclusions, or typical scenarios, leaving the agent to infer usage from the tool name alone.

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