List 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, and it discloses almost nothing. It does not state that this is a read-only listing operation, does not describe pagination behavior despite cursor/page_size params, and gives no sense of result ordering or volume.

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 short sentence with no filler or redundancy, and the core purpose is front-loaded. Its only weakness is that it is so terse it conveys little more than the tool name.

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 tool is simple (0 required params, output schema present so return values need not be explained), which lowers the bar. Even so, for a listing tool with pagination semantics and several sibling list/get tools, the description is barely complete enough to route an agent correctly.

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 cursor and page_size fully documented in the schema itself, including the notable detail that cursor makes all other arguments ignored. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 clear verb and resource ("List ... webhooks"), but it essentially restates the title "List Webhooks" and adds only the word "configured." It offers no differentiation from siblings like list_webhook_logs or get_webhook, so an agent cannot tell from the text why it would pick this over the alternatives.

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?

There is no guidance on when to use this tool versus get_webhook, list_webhook_logs, or ping_webhook. No prerequisites, no mention of the paginated listing context, and no exclusions are given.

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