Verify Webhook Signature

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

Discloses public key fetch-on-first-call caching behavior and env var override, adding value beyond annotations (readOnlyHint, idempotentHint). No contradiction with 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?

Two sentences: first explains purpose, second provides critical usage guidance. Every sentence earns its place; no redundancy.

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?

Lacks description of return value (e.g., boolean, object). With no output schema, the agent must infer behavior. Sufficient for basic usage but incomplete for advanced handling.

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 description reinforces schema descriptions without adding significant new constraints. Baseline 3 is appropriate.

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?

Clearly states 'Verify a Lexware webhook X-Lxo-Signature' with specific algorithm (RSA-SHA512, base64). Distinct from all sibling tools which deal with CRUD operations on articles, contacts, invoices, etc.

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?

Explicitly instructs to pass exact raw HTTP body bytes and warns against JSON round-tripping. Also explains caching and production override. No exclusions needed as no sibling provides alternative verification.

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