List webhooks

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

Annotations already declare readOnlyHint=true, but the description adds meaningful behavioral detail: it never returns signing secrets, and it exposes delivery health fields. This goes beyond the annotation's safety signal and helps an agent understand what this endpoint will and will not provide.

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 two sentences with no filler. The core listing behavior is front-loaded, and the important exception about signing secrets is placed immediately after, followed by the practical use case.

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?

With no parameters, no output schema, and read-only annotations, the description carries the responsibility for explaining the operation's results. It covers what is returned, what is intentionally excluded, and the primary use case, making the tool fully callable by an agent.

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 has zero parameters and schema description coverage is 100%, so there are no parameter gaps for the description to fill. The 4 baseline for zero-parameter tools applies, and the description adds relevant context about the returned payload instead of parameter details.

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 names a specific verb and resource: 'List your registered webhook endpoints.' It also enumerates the returned data (subscribed events, active status, delivery health), which clearly distinguishes it from create_webhook and delete_webhook among the sibling tools.

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 a concrete use case: 'Use this to find an endpoint's uuid before deleting it.' It also clarifies when signing secrets are available, implicitly directing agents to endpoint creation or secret rotation rather than this listing tool. It does not explicitly name alternatives or when-not-to-use, but the guidance is clear.

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