list_realtime_sessions

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only repeats the verb 'List,' implying a read-only collection operation. It does not mention pagination, ordering, filtering, scoping by account/app, or response shape. No meaningful behavioral traits beyond the operation name are disclosed.

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 very concise and front-loaded with no filler or redundant phrasing. It is not bloated, but it is terse enough that it provides only the operation and resource, leaving other useful context unstated.

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 simple two-parameter list tool with fully described schema parameters, this is minimally viable. However, the description does not explain that sessions are scoped to the account_id/app_id pair, and with no output schema it gives no indication of the response shape or pagination behavior. These gaps make it adequate but not complete.

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%, with both account_id and app_id having descriptions in the input schema. The tool description itself adds no parameter semantics, but because the schema already documents the parameters fully, the baseline of 3 is appropriate.

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 clearly states a specific verb ('List') and a specific resource ('Realtime Kit sessions'), so an agent knows what operation is being performed. It does not explicitly contrast itself with closely related siblings such as list_realtime_recordings or get_realtime_session, but the resource name is specific enough to distinguish it from other Realtime resource types.

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 provides no guidance on when to use this tool versus alternatives. It does not mention get_realtime_session for retrieving a single session, nor does it clarify what distinguishes listing sessions from listing meetings, recordings, or other Realtime resources. The only usage cue is the verb 'List' itself.

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