bulk_delete_raindrops

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

The description states 'Permanently delete' indicating irreversibility, which is a behavioral cue. However, with no annotations provided, it fails to disclose other important traits such as authorization requirements, partial failure handling, rate limits, or side effects like cascading deletions.

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?

Two sentences with no waste. The action is front-loaded, and a critical constraint (non-empty ids) follows immediately. Minor improvement could be more specificity on the resource type.

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?

Given the presence of an output schema (not shown), return values are covered. However, the description lacks usage guidelines, behavioral transparency, and full parameter semantics, leaving the agent underinformed for a destructive tool.

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?

The description adds value by specifying that 'ids must be non-empty', which is not evident from the schema. However, it provides no explanation for 'collection_id', leaving it ambiguous. Since schema coverage is 0%, the description partially compensates but is incomplete.

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 (permanently delete) and the resource (multiple bookmarks/raindrops). It effectively distinguishes from the sibling 'delete_raindrop' by implying multiplicity. However, it could be more explicit that it operates on bookmarks within a specific collection.

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?

No guidance on when to use this tool versus alternatives like 'delete_raindrop' for single deletions, or other bulk operations. There is no mention of prerequisites (e.g., requiring collection_id) or context for batch behavior.

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