Delete a call recording

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: the deletion is permanent, the audio cannot be restored, and the call is gated by an environment flag plus an explicit confirm. It does not describe behavior on a nonexistent/already-deleted id or the response, keeping it at 4.

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?

Three short sentences, each carrying distinct load: action and scope, irreversibility, and gating. The most decision-critical facts (permanent, unrecoverable) are front-loaded.

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 two-parameter destructive tool with no output schema and safety already covered by annotations, the description supplies the irreversibility warning and the feature/confirm gating an agent needs before calling. It omits only error/edge-case behavior, which is a minor gap.

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?

Schema coverage is 50% – the confirm parameter is well documented in the schema, but recording_id has only a regex pattern and no prose. The description's 'DELETE /Recording/{id}/' hints at the id parameter and restates the confirm gate, adding modest meaning but not compensating for the undocumented recording_id.

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 states a specific verb and resource ('Permanently delete one call recording'), names the scope ('from this Vobiz account'), and even gives the underlying endpoint DELETE /Recording/{id}/. An agent can immediately distinguish it from list_recordings or get_call_recording among the siblings.

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?

It states two concrete preconditions for use: the VOBIZ_ENABLE_PROVISIONING gate and confirm: true. That is clear when-to-use guidance, but it never names alternatives (e.g., use get_call_recording to inspect before deleting) or says when not to use it, so it falls short of a full 5.

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