List webhook subscriptions

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

The description adds substantial behavior beyond the readOnlyHint annotation: it notes that secret values are never returned, empty filter lists mean 'all', pagination uses a cursor, an Admin token is required, and a 404 indicates webhooks are not enabled. This is rich, non-obvious behavioral context.

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 information-dense with no filler: each sentence adds a distinct fact (contents, filter semantics, pagination, auth, error meaning). The main action and scope are front-loaded, and the supporting details are compact.

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?

With no output schema, the description carries the burden of explaining what the response contains and how the tool behaves. It covers the listed fields, filter semantics, pagination, required permissions, and a special error condition, which is complete for a list operation.

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, so the schema already documents limit and cursor. The description adds general pagination context but no parameter-specific meaning beyond what the schema provides, so the baseline 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?

Description uses a specific verb ('List') and a clear resource ('the organization's outbound webhook subscriptions'), and enumerates the included fields. It is easily distinguishable from siblings like list_webhook_deliveries because it focuses on subscriptions rather than delivery attempts.

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 provides clear context: it lists subscriptions, is paginated via cursor, and requires an Admin token. It does not explicitly name an alternative tool or state when not to use it, but the context and sibling names make the intended use clear enough.

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