notion_create_webhook

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

Description only mentions routing through an API path and authentication scopes. No disclosure of side effects, idempotency, error behavior, or other traits beyond what is implicitly known from the operation name. With no annotations, the description provides insufficient 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?

Description is short (3 sentences) with no fluff, but its brevity sacrifices informativeness. Structure is acceptable but front-loading is not leveraged.

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?

Despite having an output schema (not shown), the description lacks explanation of return values, success/failure indicators, or usage examples. For a creation tool, it is incomplete.

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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation', but the schema has 0% description coverage. The description adds minimal meaning; it doesn't specify expected keys or structure (e.g., URL, events).

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 restates the operation name 'create_webhook' without explaining what a webhook is or what creating one does. No distinction from sibling tools like 'notion_delete_webhook' or 'notion_list_webhooks'.

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. No prerequisites, context, or scenarios for webhook creation are provided.

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