deleteTags

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't specify whether this action is reversible, what permissions are required, whether it affects all users' bookmarks or just the current user's, or what happens when tags are deleted from bookmarks (do bookmarks lose those tags entirely?).

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, efficient sentence with zero wasted words. It's appropriately sized for a simple operation and front-loads the essential information (action and target).

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 operation with no annotations and no output schema, the description is insufficient. It doesn't explain the consequences of deleting tags from bookmarks, whether this affects bookmarks across all collections or just specific ones, what the response looks like, or any error conditions. The optional collectionId parameter's effect on scope remains ambiguous.

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%, so the schema already documents both parameters (tags as required array, collectionId as optional number). The description mentions 'all bookmarks' which implies global scope, but doesn't clarify how the optional collectionId parameter modifies this scope or what happens when it's omitted versus provided.

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 the action ('Delete') and target resource ('tags from all bookmarks'), providing a specific verb+resource combination. However, it doesn't differentiate from the sibling tool 'deleteTag' (singular vs plural), which could cause confusion about when to use each tool.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'deleteTag' (singular) and 'bulkTagBookmarks' available, there's no indication of whether this tool applies to all bookmarks globally, within a collection, or how it differs from other deletion/tagging operations.

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