list-webhooks

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

Annotations already indicate readOnlyHint=true, and the description adds useful operational context: the GET method, the API path, and the required webhooks:read scope. This goes beyond the annotation without contradicting it, though return format and pagination behavior are left to the schema.

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 compact sentence that front-loads the core action and resource, then appends the endpoint and scope. Every element earns its place; there is no filler.

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 read-only list operation, the description is complete enough: it identifies the resource, method, path, and permission scope, while the schema covers pagination and search. It does not describe the exact response envelope, but 'List' plus the absence of an output schema makes that a minor gap.

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 q, page, and itemsPerPage already documented clearly. The description itself adds no parameter-level detail, which is acceptable because the schema carries the full burden.

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 specific verb ('List'), a clear resource ('outbound webhook endpoints'), and the exact HTTP method and path. This also distinguishes it from sibling tools like create-webhook, get-webhook, update-webhook, and delete-webhook.

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 clear context by naming the endpoint and the required scope, making it obvious this is the list operation for webhooks. It does not explicitly discuss when to prefer get-webhook over list-webhooks, but the list-versus-get distinction is reasonably inferable from the resource name.

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