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

The description discloses the permanent and destructive nature of the operation, the need for separate memories:delete authorization, and the requirement for destructive host confirmation. This adds valuable context beyond the annotations, which already indicate destructiveness, by explaining the security and confirmation flow.

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 concise, using four short sentences that each carry essential information: usage precondition, action, alternative, and authorization requirement. There is no fluff or redundancy.

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 destructive nature of the tool, the description fully covers when to use it, what it does, its alternative, and prerequisites such as user confirmation and authorization. The presence of an output schema means return values do not need to be explained in the description.

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 parameter 'confirmation' is fully documented in the schema with an enum and a clear description. The tool description reiterates the confirmation phrase but adds no new information beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 that the tool permanently deletes every memory in the OAuth-selected vault, using a specific verb and resource. It also distinguishes itself from delete_memories, which handles specific items, removing ambiguity.

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?

Explicitly provides the exact conditions for use: the user must explicitly request a full-vault deletion, receive a permanent warning, and provide the confirmation phrase in a later turn. It also directs the user to delete_memories for targeted deletions, offering a clear alternative.

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