list_webhooks

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'List' implies a read-only operation, which is reasonably transparent for a simple listing tool. However, it does not disclose any pagination, ordering, rate-limit, or authentication behavior beyond what the output schema may imply.

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?

A single front-loaded sentence that communicates the core action, resource, and filtering capability with no filler. Every word contributes meaning.

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 listing operation with no required parameters and an output schema provided, the description is nearly complete. It covers what the tool does and the available filters. It lacks only minor contextual details like pagination or exact filter matching behavior, but those are not critical for basic invocation.

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 0%, so the description must compensate. It explicitly indicates that 'channel' and 'app' are optional filters, which adds meaning beyond the raw schema by defining their role as filters rather than required inputs. It doesn't specify value formats, but the parameter names are self-explanatory.

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 specific verb ('List') with a clear resource ('registered webhooks') and indicates optional filters. It distinguishes itself from sibling tools by resource: list_webhook_deliveries is about deliveries, while register_webhook/trigger_webhook are about creating and triggering webhooks.

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 implies usage by stating it lists webhooks with optional channel/app filters, but it provides no explicit guidance on when to choose this tool over alternatives, no exclusions, and no mention of prerequisites. Sibling tools like list_webhook_deliveries could be confused with this one without additional context.

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