Send Delete

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

The description explains that the operation is destructive for the Send and its shared content but does not delete associated vault items. Annotations already indicate destructiveHint: true, but the description adds context about what is specifically destroyed and what is preserved. It also mentions the return payload.

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 consists of two concise sentences. The first sentence states the action and method, and the second adds important nuances about destructiveness and return value. No superfluous words.

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 tool has only one parameter and no output schema, the description provides sufficient context: the action, destructive impact, what is not affected, and the nature of the return value. It addresses all key aspects for an agent to use the tool correctly.

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 single required parameter 'id' is described as 'Stable Bitwarden object id returned by list/search/get/create tools.' This adds context beyond the schema's description, clarifying the id's origin and stability. Since schema coverage is 100%, the baseline is 3, and the description provides meaningful additional guidance.

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 a Bitwarden Send by id through bw send delete.' It specifies the resource (Send) and the method. This distinguishes it from sibling tools like keychain_delete_item which delete vault items, not Sends.

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 indicates when to use (to delete a Send) and clarifies what it does not affect (vault items). However, it does not explicitly mention when not to use or suggest alternatives like keychain_send_edit for modifications.

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