list_webhooks

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

Annotations already declare readOnlyHint=true, and the description is consistent. The description adds a note about webhooks sending POST requests, which describes the domain, not the tool's behavior. It does not disclose pagination or filtering specifics beyond what the schema provides, but annotations cover safety.

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 short sentences, front-loaded with the purpose. The second sentence about webhook behavior is extra but not excessive. It is concise and to the point, with no redundant information.

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 list tool with four well-documented parameters, readOnlyHint annotation, and no output schema, the description plus schema provides sufficient context. It lacks an explicit statement about return format, but the name and schema imply a list of webhooks. Overall, it is complete for the tool's complexity.

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%, so all four parameters (page, fields, status, per_page) are documented in the schema. The description adds no additional parameter semantics, but the baseline of 3 applies because the schema carries the full weight.

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' with the resource 'webhooks', clearly identifying the operation. It also briefly explains what webhooks are, adding domain context. This distinguishes it from get_webhook (single), create/update/delete webhooks, and other list 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 makes the use case clear: to list webhooks. It does not explicitly mention alternatives like get_webhook for a single webhook or exclude other operations, but the context implies it is the listing tool. No when-not-to-use guidance is provided, but this is a simple read operation.

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