delete_zoom_meeting

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

No annotations are provided, so the description carries the full burden. It merely states 'Delete a Zoom meeting' without disclosing whether the action is permanent, requires specific permissions, or has side effects (e.g., deleting recordings or associated data). The return type is mentioned, but the destructive nature and potential irreversible impact are not explicitly communicated.

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 extremely concise and well-structured: a clear one-line purpose followed by Args and Returns sections. Every sentence adds value, and it is front-loaded with the core action.

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?

This is a simple, single-parameter delete operation. The description states the return type ('dict with confirmation message'), and an output schema exists. Given the simplicity and available structured information, the description is complete enough 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?

There is only one parameter, meeting_id. The description explains it as 'The Zoom meeting ID to delete,' which adds minimal meaning beyond the schema (it doesn't say what format the ID takes or how to obtain it). Since schema description coverage is 0%, the description provides some reinforcement but does not fully compensate with additional semantic detail.

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 uses a specific verb ('Delete') and resource ('Zoom meeting'), clearly stating the tool's function. It distinguishes from sibling tools like create_zoom_meeting, get_zoom_meeting, and list_zoom_meetings by being the only deletion operation for Zoom meetings.

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 clearly implies the use case: when a Zoom meeting needs to be deleted. It does not explicitly mention alternatives or exclusions, but the context is clear enough given the sibling tools. However, it lacks explicit 'when not to use' guidance or prerequisites, so it doesn't fully earn a 5.

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