KB Sync Webhook Notification (Deprecated)

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

Annotations already indicate readOnlyHint=false and openWorldHint=true. The description only adds deprecation status and does not disclose what happens to the payload (processing, side effects, response format). It adds minimal behavioral context beyond the 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 a single, concise sentence with the deprecation notice front-loaded. It contains no fluff, though it could have briefly mentioned an alternative tool for the deprecated functionality.

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 webhook receiver with one optional object parameter and no output schema, the description is too thin. It lacks usage context, deprecation replacement, accepted payload structure, and what the caller should expect after invoking the tool.

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 coverage for the single 'payload' parameter is 100% with a clear description ('Raw webhook notification payload'). The tool description does not add new parameter meaning, but the schema already fully documents it, so the baseline score of 3 applies.

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 receives a KB Sync webhook notification payload, using a specific verb and resource. However, it does not differentiate from the sibling lyzr_kb_sync_webhook_validation tool or explain how 'notification' differs from 'validation'.

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. The '[deprecated]' marker implies it should not be used but does not mention a replacement tool or the webhook notification flow context.

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