webhook_list_recent

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

No annotations are provided, so the description carries the full burden; it does state 'Read-only', which is a genuine safety disclosure. But it says nothing about ordering guarantees, retention window, pagination, or auth requirements, and the meaning of 'recent' is left undefined.

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?

Front-loaded with the core action and the read-only flag, which is good, but the second sentence ('Shows the latest events captured by the webhook receiver') largely restates the first, and the third adds only a generic debugging rationale. It is not bloated, but it does not fully earn its length.

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?

An output schema exists, so return-value explanation is unnecessary, and the tool is low complexity with one optional parameter. Still, the description omits any differentiation from the sibling webhook_list_events and gives no 'recent' definition, which an agent would need to call it confidently.

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 description coverage is 100% and the single 'limit' parameter is documented in the schema with a default of 50, so the baseline is 3. The description adds no guidance on the limit, such as a maximum or the effect of omitting 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?

Names a specific verb (List) and resource (recent webhook events received by the receiver), and the second sentence clarifies it returns the latest captured events. However, it never distinguishes itself from the sibling 'webhook_list_events', which sounds nearly identical, so an agent cannot tell which to pick without opening both schemas.

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?

'useful for debugging and verifying webhook delivery' implies a use case but gives no explicit when-to-use versus when-not, and no mention of the near-identical sibling 'webhook_list_events' or 'webhook_test_rule'. Usage is suggested rather than specified.

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