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

Even though the destructiveHint annotation already flags destructive behavior, the description goes far beyond it by explaining what is destroyed (avisos, notas, documentos), that it is irreversible, and the required login. This is high-value behavioral context not present in structured 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 dense and well-structured, with each sentence carrying essential information. It is slightly longer than necessary but avoids fluff, front-loading the critical permanent deletion fact and then providing procedural and alternative guidance.

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, irreversible operation with no output schema, the description provides a complete operating picture: what is deleted, the confirmation protocol, authentication needs, and a clear alternative. The agent has all necessary context to safely invoke this tool without further documentation.

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 reinforces the schema for the 'nombre' parameter by specifying it must match listar_mis_alertas, and it explains the confirmar parameter's role in the two-step confirmation workflow. While the schema already covers 100% of parameters, the description adds practical usage guidance that helps the agent sequence calls correctly.

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 tool deletes an alert permanently along with its history ('Borra una de tus alertas de forma PERMANENTE, junto con todo su histórico'). It names the specific resource (alerta) and shows scope, distinguishing it from sibling tools like pausar_alerta by explicitly directing users to the alternative.

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?

Provides explicit usage context: when to use (permanent deletion), when not to use (if only pausing, use pausar_alerta), a required authentication step ('Requiere iniciar sesión'), and a clear two-step confirmation flow with confirmar=false then confirmar=true. This fully guides the agent on when and how to invoke the tool.

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