Notes Delete Folder

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

The annotations already declare destructiveHint=true, so the agent knows the operation is destructive. The description adds no additional behavioral context: it does not disclose whether deletion is recursive, whether the folder must be empty, whether it affects notes inside the folder, or whether it can be undone. However, because the destructive annotation is present and the description does not contradict it, a baseline score of 3 is appropriate; the description simply contributes nothing beyond what the annotation already conveys.

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 and front-loaded, but brevity is not conciseness when it carries no information. 'Delegated Apple domain tool' is boilerplate that applies to presumably every tool in this MCP, and naming the tool again is redundant. The single sentence earns no place because it repeats the name and the MCP exposure rather than describing behavior.

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 destructive tool with one required parameter, no parameter documentation, and no behavioral details, the description is severely incomplete. An output schema exists, but that does not help an agent decide whether to call this tool or how to construct the folder_id. There is also no mention of how this differs from notes_delete_note, files_delete_path, or any other deletion tool in the sibling list. This is a minimum-viability failure for a destructive operation.

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 carries the full burden of explaining the folder_id parameter, but it says nothing about it. The schema only provides the name and type (string), leaving the agent to guess what a valid folder_id looks like, where to obtain one, and whether it refers to a Notes account-level folder or a nested folder. With one required parameter and zero coverage, the description should have provided at least a format hint or a pointer to notes_list_folders.

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 is a tautology: 'Delegated Apple domain tool 'notes_delete_folder' exposed through Apple-Tools-MCP.' It merely restates the tool name and the fact that it is exposed through the MCP bridge. It does not state what the tool does, what a folder is in this context, or how it distinguishes itself from sibling tools such as notes_delete_note, files_delete_path, or reminders_delete_list. The title 'Notes Delete Folder' adds no information beyond the name.

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 indication of when to use this tool instead of alternatives such as notes_delete_note, notes_rename_folder, or notes_move_note. The description says nothing about prerequisites (e.g., whether the folder must be empty), the scope of deletion, or the intended workflow. An agent receives zero guidance on selecting this tool over its siblings.

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