Borrar mensaje de voz

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds '⚠️ Acción irreversible' (irreversible action), reinforcing the destructive nature. However, it does not disclose auth requirements, rate limits, or detailed side effects beyond deletion.

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 a single sentence with a warning emoji, concise and front-loaded. It effectively communicates the action and irreversibility without extra verbiage.

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?

The description covers the action and irreversibility, but does not mention expected output (e.g., success confirmation), prerequisites (e.g., voicemail must exist), or error conditions. For a simple delete tool with no output schema, this is minimally adequate.

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 input schema has two string parameters (extensionId, voicemailId) with 0% schema description coverage, meaning the schema provides no semantic help. The description does not mention or explain these parameters, leaving agents without guidance on what values to provide.

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 'Elimina un mensaje de voz del buzón de una extensión' (Deletes a voicemail message from an extension's mailbox), specifying the verb and resource. Among sibling tools, pbx_delete_voicemail is the only delete operation for voicemails, distinguishing it from list, get, download, and mark tools.

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 delete versus other actions (e.g., marking as read/unread). The description only warns of irreversibility but does not provide context for appropriate use or mention alternatives.

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