apple_notes_create

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

Annotations already declare the mutation profile (readOnly=false, idempotent=false, destructive=false, openWorld=true), so the bar is lower. The description still adds real value: the title is escaped and rendered as a heading, the body is optional HTML, and the note 'may sync to iCloud', which contextualizes the openWorld hint. It stops short of stating what happens on duplicate titles or sync failure.

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?

Two sentences, verb front-loaded, no filler. The iCloud sentence is short, but 'May sync' is a soft hedge that could be stated more decisively.

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?

No output schema, so return values need not be explained, and annotations cover the safety profile. However, for a create tool with two required params and zero schema descriptions, the definition leaves the agent without guidance on obtaining folderId or on what the sync behavior means operationally.

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 must carry parameter meaning, and it does map all three: folderId ('explicit folder'), title (escaped heading), htmlBody (optional HTML). It omits how folderId is sourced and says nothing about the empty-string default for htmlBody besides 'optional', so it is good but not exhaustive.

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?

States a specific verb and resource ('Create a note'), plus scoping ('in an explicit folder') and content shape (title heading, optional HTML body). It does not distinguish itself from close siblings like apple_notes_update or apple_textedit_create, but the purpose itself is unambiguous.

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 phrase 'in an explicit folder' hints that a valid folderId is a prerequisite, but the description never says when to use this versus apple_notes_update, nor how to obtain a folder id (e.g., apple_notes_list_folders). No exclusions or alternatives are given.

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