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

Annotations only mark readOnly/idempotent/destructive as false; the description adds the important behavioral facts: the result is asynchronous, it consumes meeting minutes, it is rate limited to 5 bots/hour, and OAuth 2.1 user auth is required. No contradiction with annotations.

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?

Five short sentences each carry distinct value: what it does, uniqueness/single-URL limit, minutes consumption, async follow-up, and auth. It is front-loaded with the core action and contains no filler.

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 creation tool with no output schema, it covers platforms, side effects, rate limiting, auth, the async nature of the result, and the tracking path. An agent has enough information to invoke it correctly and understand what to expect.

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 description coverage is 100%, so the schema already documents title, language, meeting_url, and scheduled_time with descriptions. The description mostly reinforces the single-URL constraint already present in the schema and does not add parameter-level semantics beyond it.

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 opens with a precise verb and resource: 'Send a bot to join ONE Zoom, Google Meet, Teams or Webex call and record it, producing a speaker-attributed transcript after the call ends.' This clearly distinguishes it from the many list/status/cancel siblings as the active meeting-bot creation tool.

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 explicitly says when to use it ('the only tool here that creates new transcription work'), what it does not accept ('never a list'), and what to do next ('track it with list_scheduled_meetings'). Rate limits and account-minute consumption add decision-relevant constraints beyond the schema.

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