list_webhooks

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

The description states the tool lists all webhooks, which is a safe read operation, but with no annotations provided, it carries the full burden for behavioral disclosure. It does not mention whether there is pagination, rate limiting, or any other operational details, though the simplicity of the tool limits the need for more.

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, front-loaded sentence of three words. It conveys exactly what the tool does with zero waste.

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 tool with no parameters, no annotations, and no output schema, the description 'List all webhooks' is fully adequate. There are no complex behaviors to explain, and the sibling list does not reveal any missing context.

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, so the schema is fully covered and there is nothing to explain. The description adds no parameter information because none is needed.

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 'List all webhooks' uses a specific verb ('List') and resource ('webhooks'), clearly distinguishing it from sibling tools like create_webhook, delete_webhook, and test_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 makes it obvious this is the tool for listing webhooks, and the simple context implies it should be used when a user wants to see all webhooks. It does not explicitly state when not to use it, but no alternative listing tool exists among siblings, so the guidance is clear enough.

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