list_webhooks

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

No annotations are provided, so the description carries the full burden. The word 'List' suggests a read-only operation, but the description does not explicitly confirm no side effects, mention pagination behavior, or disclose any caveats. It adds minimal behavioral context beyond what the name alone suggests.

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 concise sentence that front-loads the primary purpose and lists the return fields. Every word is informative, with no redundant or filler content.

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?

The description names the exact fields returned (URL, action, entity type, status), which helps the agent understand the output despite lacking an output schema. However, it does not explain pagination behavior or whether all fields are always included, leaving minor gaps for a simple list tool.

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% for both parameters (limit and offset), so the schema already documents their semantics. The description does not add additional context about parameters, such as how pagination works or the impact of the limit, so the baseline score of 3 is appropriate.

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 clearly states the action ('List all registered webhooks') and the resource (webhooks), with a specific verb and scope. It distinguishes itself from sibling tools (create_webhook, update_webhook, delete_webhook) by focusing on listing existing webhooks.

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 does not explicitly mention when to use this tool versus alternatives. However, the verb 'List' and the resource 'webhooks' imply that this is the appropriate tool for retrieving registered webhooks, making usage context implied rather than explicit.

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