create_zoom_meeting

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

Description goes far beyond annotations by detailing the human-approval gate, the fact that the first call executes nothing, the approved-arguments-not-second-call rule, expiration, deduplication, rate limiting, audit logging, the waiting room behavior, and the external requirement of Zoom being connected. This gives the agent a clear model of side effects and safety even though destructiveHint is true.

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 but front-loaded, and every sentence carries essential information for a complex, human-approved, two-phase tool. Rather than padding, it covers invocation flow, pending-request behavior, rate limits, audit, privacy, output shape, and prerequisite in a compact block.

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 tool with no output schema, the description explicitly states the return shape ({id, join_url, password}), the main statuses (approval_required, awaiting_approval, rate_limited), and the prerequisite. Combined with the thorough input schema, an agent has everything needed to call and interpret 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?

The input schema already covers all parameters with 100% description coverage, but the tool description adds crucial semantics for request_id: it must be omitted on the first call, the approved payload wins over the second call's arguments, and deduplication/expiry behavior. This is meaningful value beyond the schema, though the other parameter details are left to the schema.

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 opening sentence states a specific verb and resource ('Create a Zoom meeting on the user's connected Zoom account') and the key return value ('return its join link'). This unambiguously distinguishes it from sibling tools like create_event or send_mail, especially with the later note to share the join_url via send_mail/reply_mail.

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 explains the two-phase invocation workflow (first call without request_id, second call with approved request_id), the prerequisite that Zoom must be connected, and the follow-up action of sharing the join_url via send_mail/reply_mail. It does not explicitly state 'use create_event for calendar events' or list when-not-to-use scenarios, but the context is strong enough for an agent to select and invoke it correctly.

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