notion_delete_webhook

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

No annotations are present, so the description must carry the full burden. It indicates a destructive delete operation but does not disclose irreversible consequences, required permissions, rate limits, or what happens after deletion. The behavioral impact is underdescribed.

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 brief (three sentences) and the routing information is front-loaded. However, conciseness is achieved at the cost of missing critical usage and parameter details. Every sentence serves a purpose but collectively insufficient.

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 that output schema exists (context signals), return values are not needed. However, for a destructive operation like deleting a webhook, the description should specify what identifies the webhook (e.g., ID) and any required context. The description is incomplete for an agent to 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?

The single parameter `arguments` is described as a JSON string of arguments for the connector operation, but no details are given about the expected structure (e.g., webhook ID). With 0% schema description coverage, the description fails to add meaningful guidance for constructing the parameter.

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 identifies the operation as deleting a webhook, but it does not specify which webhook (by ID or name) and does not distinguish from sibling delete webhook tools like clio_delete_webhook or jira_delete_webhook. The purpose is clear generically but lacks specificity.

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 no guidance on when to use this tool versus alternatives, no when-not conditions, and no prerequisites. It only describes routing and arguments, leaving the agent without context for appropriate use.

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