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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the diagnostic framing but says nothing about retention window, pagination, or what the log entries contain, which is the behavior an agent most needs for a diagnostics tool.

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?

Three short sentences, front-loaded with the action and then the trigger condition. The final sentence ('preferred to guessing whether delivery occurred') is mildly redundant rationale but still short and non-repetitive.

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?

Complete for a two-parameter, read-only diagnostic tool whose safety profile is fully covered by annotations and whose parameter semantics are largely in the schema. No output schema exists, so the description need not explain return values.

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 50%: destination_id carries a rich schema description including the warning to use the Nilyo ID rather than the remote endpoint ID, while limit has constraints but no prose. The description adds nothing about either parameter, so it does not compensate for the undocumented limit, but the schema itself remains informative.

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 ('Inspect') and resource ('recent webhook delivery attempts for this destination'), which is clearly distinct from sibling tools like webhook_get_destination or webhook_test_destination. It does not explicitly name a sibling to contrast with, but the purpose is unambiguous.

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 concrete triggering conditions: use when an agent/n8n receiver did not wake or a test event was not observed. This is clear diagnostic context. It stops short of naming explicit alternatives (e.g. webhook_test_destination) or stating when not to use it.

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