Apple Preview Create Note With Defaults

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description mainly reinforces that this is a preview rather than an actual create. It adds some behavioral context by specifying that the configured default notes folder is used, but does not describe edge cases such as missing configuration or folder_id override behavior.

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?

One sentence with no filler. The key qualifying behavior (preview) is front-loaded, and every word earns its place.

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 provided annotations and output schema cover safety and likely return shape, so the minimal description is workable. However, it omits prerequisites or caveats around the configured default notes folder and does not explain whether the optional folder_id parameter overrides it, which an agent may need to know.

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 for parameter semantics, but it only mentions the default notes folder. It does not clarify how title, body_html, body_text, tags, or especially folder_id interact with the default-folder behavior, leaving important invocation semantics ambiguous.

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 states a specific action ('Preview how Apple-Tools will create a note') and scopes it to the configured default notes folder. This clearly distinguishes it from actual creation and from previewing other resources, though it does not explicitly name the corresponding create alternative.

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 use of 'Preview' implies a dry-run before actual note creation, and the reference to defaults sets context. However, there is no explicit guidance about when to use this tool instead of apple_create_note_with_defaults or how it relates to the other apple_preview_* tools.

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