List webhooks

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds 'configured' and 'and their subscriptions,' providing minor behavioral context but no mention of pagination, ordering, or other response traits. It does not contradict annotations.

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 sentence that leads with the verb 'List,' immediately clarifying the operation. It contains no filler words and is appropriately sized for a simple list tool.

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?

Given the tool's simplicity (zero parameters, read-only, no output schema), the description is complete. It clearly states what is listed ('webhook endpoints and their subscriptions') and is sufficient for an agent to invoke correctly without needing additional 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 has zero parameters, and the schema coverage is 100% (no properties). Baseline for zero parameters is 4, and the description does not need to elaborate on parameter syntax since none exist.

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 a clear resource: 'configured webhook endpoints and their subscriptions.' This distinguishes it from sibling tools like list_webhook_events, create_webhook, update_webhook, and delete_webhook by clarifying it covers endpoints and subscriptions, not events or mutations.

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?

Usage is implied by the action: use this tool to view webhook endpoints and their subscriptions. However, it does not explicitly state when to prefer this over alternatives like list_webhook_events or get_endpoint_details, nor does it mention any exclusions.

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