List webhook endpoints

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

The description adds context beyond the annotations (readOnlyHint=true, openWorldHint=true) by specifying that it returns both active and revoked endpoints, and that it applies to the calling account. No contradictions with 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?

Two concise sentences: the first states the primary function, and the second provides usage guidance. Every sentence earns its place; no wasted words.

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 zero-parameter read-only tool, the description fully covers what the tool does, what it returns (webhook endpoints), and how to use it (inspect before register, find id to revoke). No gaps remain.

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 no parameters, and schema coverage is 100%. Baseline for 0 parameters is 4. The description does not need to add parameter details, and it correctly implies no inputs are needed.

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 tool lists the calling account's webhook endpoints, both active and revoked. It uses a specific verb 'list' and resource 'webhook endpoints', which distinguishes it from sibling tools like qmailing_register_webhook (create) and qmailing_delete_webhook (delete).

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 explicit usage scenarios: 'use to inspect existing subscriptions before registering a duplicate, or to find an id to revoke.' This gives clear context for when to use this tool vs. alternatives (register, delete) and includes practical motivations.

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