notion_delete_webhook

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

Annotations already disclose the critical safety profile (destructiveHint=true, readOnlyHint=false, idempotentHint=true), so the bar is lower. The description adds useful governance context — the 'exact project/account governed connector authority' routing, Spring's verification of the claimed 'effect', and approval_ref being required 'when resuming a write' — but it never discloses what happens at the Notion end (webhook removed, irreversibility, impact on subscribed integrations). No contradiction 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?

The description is compact (~100 words) and well-structured: identity line, routing constraint, then a flat Args list with each parameter on its own line. Every sentence earns its place, and the structure makes the plumbing parameters easy to scan, though the content is somewhat boilerplate-generic across connector tools.

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?

An output schema exists, so return values need not be explained, and annotations cover the destructive/idempotent profile. Still, for a 7-parameter destructive operation with an undocumented schema, the description omits the actual contract of the 'arguments' payload (what identifies the webhook to delete), any prerequisites (webhook must exist), and the concrete effect of deletion on Notion.

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?

With 0% schema description coverage, the description carries the full burden, and it does provide one-line semantics for all 7 parameters (e.g., 'Stable business-action identity' for idempotency_key, 'Approved platform task UUID when resuming a write' for approval_ref). However, the most tool-specific parameter, 'arguments', is described only as a generic 'JSON string of arguments for the connector operation' — the actual delete payload (the webhook identifier) is left to inference.

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 verb+resource is carried almost entirely by the tool name itself ('delete_webhook'); the description's opening line merely restates it as 'Notion connector operation delete_webhook' rather than explaining what deleting a webhook accomplishes. The 'Notion connector' framing does at least scope it against cross-platform siblings like jira_delete_webhook, clio_delete_webhook, and monday_delete_webhook, so it is not a pure tautology.

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?

No guidance on when to use this tool versus alternatives such as notion_list_webhooks, notion_create_webhook, or notion_update_webhook. The line 'Routes only through the exact project/account governed connector authority' is an implementation/routing constraint, not usage direction; it does not help an agent decide when deletion is the right operation.

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