delete_bulk

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

Annotations already declare destructiveHint=true, so the destructive nature is covered. The description adds useful context about the 500-entity limit and id-only operation, but does not disclose other behaviors like partial failure handling, irreversibility, or permission requirements. This is moderate extra value beyond the annotations.

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 only two sentences with the core purpose front-loaded. The phrase 'layer 1' is unexplained jargon that slightly detracts from clarity, but no words are wasted.

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 simple two-parameter destructive tool with annotations already marking it destructive, the description covers the essential scope. However, it leaves open questions about response format, partial deletions, and what 'layer 1' means, which an agent might need for safe invocation.

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?

With 50% schema description coverage, the tool description compensates by explaining that 'ids' are the entity identifiers and that all IDs belong to a single resource. It reinforces the resource parameter's meaning and clarifies the operation is id-driven, adding value beyond the bare schema.

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 uses a specific verb ('Delete') and resource scope ('up to 500 entities of one resource by id'), clearly distinguishing it from single-entity delete siblings like delete_entity. The 'by id' and 'one resource' constraints make the tool's purpose unambiguous.

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 implies bulk use through 'up to 500 entities' and 'bulk delete', but it does not explicitly name alternatives or state when to use this tool versus delete_entity or delete_card. It provides a constraint ('by id only') but leaves the selection logic to the agent.

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