List webhook endpoints

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

Annotations already declare readOnlyHint=true, so the description adds value by disclosing that 'Signing secrets are never retrievable - they are shown once, when the endpoint is created.' It also mentions health status, giving useful context about response content beyond the schema.

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 consists of three concise sentences, each serving a distinct purpose: what it lists, an important limitation, and when to use it. No redundancy or filler; every sentence earns its place.

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 has no input parameters, an output schema is present, and annotations indicate read-only behavior, the description fully covers the needed context. It explains the purpose, key limitations, and a practical use case, making it complete for an agent to select and invoke correctly.

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?

There are no parameters, so the baseline for parameter semantics is 4. The description does not need to explain parameter meanings since the input schema is empty. It correctly focuses on the tool's purpose and return value characteristics.

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 a specific verb and resource: 'List the account's webhook endpoints.' It also details what the list includes (events, health) and distinguishes itself from sibling tools like everypage_manage_webhook by focusing on listing and diagnostics rather than management.

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?

Provides a clear context for when to use the tool: 'Use this to diagnose an automation that has stopped firing.' It implies this is for reading/diagnostic purposes rather than creating or modifying webhooks, but does not explicitly name alternatives or exclusions.

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