create_note

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

With no annotations, the description must disclose behavioral traits. It states it 'creates and saves a new note,' but does not mention potential side effects, dependencies (e.g., Apple Notes must be running), or behavior on duplicate titles. For a straightforward creation action, this is adequate but not rich.

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 sentence that is direct and correctly front-loaded with the action and resource. There is no filler or wasted words, making it highly efficient for an AI agent to parse.

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 low complexity with 3 simple parameters and no output schema. The description covers the core functionality, but it does not mention what happens on success or failure (e.g., return value). Since the operation is a simple create, this is a minor gap, making the description mostly complete.

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 100% for all three parameters. The description's mention of 'title, body content, and optional folder' only restates what the schema already provides, adding no extra semantic meaning. Baseline 3 is appropriate since the schema does the heavy lifting.

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 a specific action ('Creates and saves a new note') on a specific resource ('native Apple Notes application'). It also lists the key components (title, body, optional folder), making it easy to distinguish from sibling tools like create_email_draft.

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 clear context: this tool is used for creating a note in Apple Notes. While it doesn't explicitly mention alternatives or when-not-to-use, the purpose implies its primary use case. It lacks explicit exclusions or comparisons to similar tools like run_applescript, so a score of 4 is appropriate.

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