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

Annotations already cover safety with readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds useful behavioral context: the HMAC secret is intentionally omitted, and the call requires webhooks:read API-key scope. It does not describe pagination or response shape.

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 sentences, front-loads the main action, and every sentence adds useful information: one establishes the list scope, the other discloses the secret omission and auth requirement.

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 read-only listing tool with rich schema coverage and annotations, the description is nearly complete: it explains scope, secret handling, and API-key scope. It could still mention pagination or return-list characteristics, but nothing critical to invocation is missing.

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 the account and workspace parameters are fully documented in the schema. The description adds no parameter-specific detail beyond general workspace scoping, which is the baseline expectation when the schema already carries parameter semantics.

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 states a specific verb and resource: list webhook subscriptions. It also scopes the result to the current workspace, which helps distinguish this from single-webhook reads and webhook delivery listings, but it does not explicitly name or route against sibling 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 does not say when to use this tool versus alternatives such as pm_get_webhook, pm_list_webhook_deliveries, or pm_get_webhook_usage. Usage is only implied by the phrase 'List all webhook subscriptions' and there are no exclusions or selection guidance.

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