Live Source Webhook Notification

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so it is known to be a non-destructive write. However, the description adds no behavioral details such as whether the call is idempotent (though idempotentHint=false is already set), what happens on success/failure, or any prerequisites. No additional context beyond annotations is provided.

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, front-loaded with the verb 'Send'. There is no fluff or redundant phrasing, making it easy to parse quickly.

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?

With one parameter and no output schema, the description should still explain what happens after sending the payload (e.g., return value, errors, side effects). It does not, so the agent cannot predict the outcome of the call. This is a significant gap for a mutation 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?

The schema has one required parameter 'payload' described as 'Webhook notification payload' with 100% coverage. The tool description adds only the example 'from a SharePoint change feed', which gives a hint about payload provenance but no further structure or validation information. Thus it meets the baseline for well-covered schemas.

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 uses the verb 'Send' with the resource 'live source webhook notification payload', which states the basic action. However, it does not explain the purpose or effect of sending the payload, nor does it distinguish this from sibling tools like lyzr_livesource_ext_webhook_get or lyzr_kb_sync_webhook_notification. The example 'from a SharePoint change feed' adds some context but leaves ambiguity about whether the agent is sending or receiving the notification.

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?

There is no guidance on when to use this tool versus the many sibling webhook-related tools. No alternatives or exclusions are mentioned. The single example does not imply a clear usage scenario beyond having a payload from a live source.

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