create_zoom_meeting

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

Goes far beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false): it discloses out-of-band human approval behind Windows Hello / Touch ID, 15-minute expiry, deduplication of identical pending requests, a 20-requests/hour refusal with status=rate_limited, and full audit logging. Critically, it warns that the executed payload is the approved arguments, not the ones passed the second time — a non-obvious behavior no annotation conveys.

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?

Front-loaded with the core action and the two-phase mechanic before the secondary branches; every sentence carries operational weight, including the rate-limit and expiry details. It is dense — one long block covering approval, dedup, throttling, return shape and two fallbacks — which costs a bit of scannability.

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 mutating, externally-visible, human-gated tool with no output schema, it supplies exactly what is missing: return payloads per branch ({id, join_url, password} vs {join_url, fixed_link: true}), failure statuses (approval_required, awaiting_approval, rate_limited), and the instruction to ask the user for a personal link when neither prerequisite exists.

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 100%, so the baseline is 3; the description nevertheless adds real meaning to request_id — that omitting it yields a preview, that the agent cannot self-approve, and that resubmitting without approval only returns awaiting_approval. It also clarifies the practical consequence of approval (meeting created with waiting room on, no participants invited), which the schema does not.

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?

States a specific verb and resource ('Create a Zoom meeting on the user's connected Zoom account') plus the side effect that matters (returns the join link). The Zoom-specific framing cleanly separates it from calendar siblings like create_event, and the fallback branches (personal fixed link, no link at all) are named explicitly.

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?

Gives explicit when-to-use routing: call once without request_id to get an approval preview, call again with the returned request_id to execute, and hand the join_url to send_mail/reply_mail 'which need their own approval.' It also states the when-not path — if a fixed personal link exists, nothing is created and no approval is needed.

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