list_webhooks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the HTTP method and basic action, offering no information about pagination behavior, return shape, ordering, or whether the response contains sensitive webhook data. This is minimal and under-disclosing.

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 extremely concise, well-front-loaded, and contains no filler. It loses a point only because it is so terse that it adds little beyond the tool name, though the endpoint reference gives it some structural value.

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 list tool with three undocumented pagination parameters, no output schema, and no annotations, the description is too sparse. It does not explain how pagination works or what the response contains, leaving important invocation details to assumption.

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%, and the description does not compensate by explaining 'after', 'before', or 'limit'. The agent cannot infer cursor semantics, value formats, or constraints from either the schema or the description.

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', and the explicit endpoint 'GET /webhooks' reinforces the collection-level operation. It is not a tautology and is naturally distinguishable from the sibling get_webhook and webhook mutation tools, though it never names an alternative.

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 given on when to use this tool versus get_webhook or other webhook tools. The intended use is weakly implied by the name and endpoint, but there is no explicit context, prerequisite, or alternative-selection advice.

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