batchDeleteBookmarks

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It confirms a destructive operation ('Delete') but doesn't disclose critical details: whether deletions are reversible, if permissions are required, what happens on partial failures, or rate limits. The 'permanent' parameter hints at trash behavior, but the description itself doesn't elaborate.

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 front-loaded with the core action and resource, making it immediately scannable. Every word ('Delete multiple bookmarks at once') directly contributes to understanding the tool's purpose.

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 batch operation with no annotations and no output schema, the description is inadequate. It lacks crucial context: error handling, response format, side effects (e.g., on linked tags/collections), and safety warnings. The agent must rely entirely on the schema for operational details, leaving behavioral gaps.

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 parameters are fully documented in the schema. The description adds no additional meaning about 'ids' or 'permanent' beyond implying batch scope. It doesn't explain ID formats, array size limits, or the implications of permanent deletion. Baseline 3 is appropriate as 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 the action ('Delete multiple bookmarks') and resource ('bookmarks'), making the purpose immediately understandable. It distinguishes from single-delete sibling 'deleteBookmark' by specifying 'multiple... at once', though it doesn't explicitly contrast with other bulk operations like 'bulkMoveBookmarks' or 'bulkTagBookmarks'.

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. It doesn't mention prerequisites (e.g., needing bookmark IDs), compare to single-delete 'deleteBookmark', or explain when batch deletion is preferable over other bulk operations like 'bulkMoveBookmarks'. The agent must infer usage from context alone.

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