Notes Create Note

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

The description discloses zero behavioral traits. With no readOnlyHint and only idempotent/destructive hints that are all false, the description carries the full burden of explaining side effects, permissions, or return behavior, but it says nothing. An agent is left completely in the dark about what invoking this tool does.

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 short, but the single sentence is boilerplate that merely restates the tool's name and exposure mechanism. It is under-specified, not concise in a useful way. No meaningful information is front-loaded or otherwise presented.

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 creation tool with four parameters, a required folder_id, and no behavioral disclosure, the description is severely incomplete. It does not explain what creating a note involves, what the output is, or what constraints apply. The rich sibling list only makes the lack of context more apparent.

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 compensate by explaining parameter meanings or relationships, but it does not. The schema provides raw names and types (title, folder_id, body_html, tags), yet the description adds no semantic value. This is a complete failure to clarify parameters.

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 only repeats the tool name in a wrapper phrase: 'Delegated Apple domain tool 'notes_create_note' exposed through Apple-Tools-MCP.' It states no verb, no resource, and no action the tool performs. An agent cannot tell what this tool does beyond what the name itself implies.

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 like notes_update_note, notes_append_to_note, or notes_create_folder. The name hints at creating a note, but the description offers no context, prerequisites, or exclusions. This is effectively no usage guidance.

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