list_realtime_meetings

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

There are no annotations, so the description carries the full burden. It only says 'List', which implies a read operation, but it does not describe response shape, pagination, ordering, scoping by account/app, authentication expectations, or any rate-limit behavior.

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 one short, front-loaded sentence with no wasted words. It is efficient, though it is so minimal that it adds little beyond what the tool name already conveys.

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 low-complexity list tool with two documented required parameters, the schema covers the basic invocation needs. However, the absence of an output schema and any detail about pagination, filtering, or the meaning of a 'Realtime Kit meeting' leaves noticeable gaps.

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% for both required parameters, account_id and app_id, so the schema already documents their meaning. The description adds no additional information about how these parameters affect the results.

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 ('List') and resource ('Realtime Kit meetings'), so an agent can tell it returns a collection of meetings. It is clear but does not explicitly differentiate itself from closely related siblings such as get_realtime_meeting or list_realtime_meeting_participants.

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?

No guidance is given for when to choose this tool over alternatives like get_realtime_meeting, list_realtime_recordings, list_realtime_sessions, or other Realtime Kit list tools. The only implicit signal is the tool name and the word 'List'.

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