list_webhooks

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

With no annotations, the description carries the full behavioral burden. It clearly signals a read-only listing operation and constrains scope to 'configured' webhooks, which is useful. However, it does not mention pagination, authentication requirements, or response shape—though none of these omissions are misleading.

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 states exactly what the tool does with no wasted words. It is appropriately sized for such a simple, parameterless operation.

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 zero-parameter read tool, the description is minimally sufficient for invocation. However, there is no output schema and no description of the returned webhook objects, pagination, or ordering, leaving an agent without full context for consuming the result.

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 tool takes zero parameters, and schema coverage is vacuously 100%. Per the zero-parameter baseline, the description need not explain parameter semantics, and the absence of parameters makes invocation unambiguous.

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 the specific verb 'List' and the resource 'configured webhooks,' clearly identifying the tool's purpose. It is semantically distinct from siblings like list_webhook_event_types, create_webhook, and delete_webhook, even without explicitly naming them.

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 provided on when to use this tool versus alternatives such as list_webhook_event_types, create_webhook, or delete_webhook. The context is inferable from the sibling names, but the description itself offers no explicit usage direction or exclusions.

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