loyalteez_validate_webhook

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the algorithm (HMAC-SHA256) and that signatures come from the X-Loyalteez-Signature header, but it never states what the tool returns on success/failure or how a validation error surfaces.

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?

Purpose is front-loaded, the crypto detail and security rationale follow, and a doc reference closes it. Four short lines with no padding.

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 mutation-free validator with no annotations and no output schema, the definition covers intent, algorithm, and the header source but omits return semantics (boolean vs. error) and any failure-handling guidance an agent would need to act on the result.

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 is 100% and the three parameter descriptions (secret, raw payload, signature header) are self-explanatory, so the schema does the heavy lifting. The description adds no parameter-level syntax or format detail beyond it.

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?

States a specific verb+resource ('Validate a webhook signature') and adds the goal ('ensure the request is from Loyalteez'). No sibling performs validation, so the tool is inherently distinct from the event/reward tools listed.

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?

Gives a clear when-to-use ('verify webhook authenticity before processing events') and a security directive ('always verify signatures'). It does not name alternatives or explicit exclusions, but none are needed for a standalone validator; the docs link is a helpful pointer.

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