list_realtime_webhooks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only repeats the verb 'List' and does not mention pagination, ordering, account/app scoping, or what the response contains. While 'List' implies a read-only enumeration, the agent is left without meaningful behavioral detail.

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 a single sentence that front-loads the verb and names the resource with no filler or redundant information. It is appropriately sized for a straightforward list tool.

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?

The operation is simple and both required parameters are documented in the schema, so the core invocation is clear. However, with no annotations and no output schema, the description could have added value by stating pagination behavior or the scope of the listed webhooks; it currently offers only the minimum viable information.

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 describes both parameters completely (account_id and app_id), so the schema covers the semantics. The description does not add any additional meaning about how the parameters relate to the list operation, which is acceptable given the 100% schema coverage.

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 uses a clear verb (List) and resource (Realtime Kit webhooks), so an agent understands the operation. It does not explicitly distinguish itself from the sibling get_realtime_webhook, but the plural 'webhooks' and verb 'List' make the basic purpose unambiguous.

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 gives no guidance about when to use this tool versus the many sibling list/get tools, such as get_realtime_webhook or list_realtime_sessions. There are no stated exclusions, prerequisites, or conditions that select this tool over alternatives.

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