List your webhook endpoints. Pass external_ref to fetch the specific bucket you created earlier under that name — this is how you re-anchor after losing the conversation, since you never need to have stored the bucket id.
| Name | Required | Description | Default |
|---|---|---|---|
| external_ref | No | Return only the bucket with this exact external_ref. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It indicates read-only behavior via 'List' and adds the re-anchor context, but it does not disclose potential side effects, auth requirements, or return format. The description goes beyond a tautology but lacks deeper behavioral detail.
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 two sentences and about 40 words. It front-loads the core function, then adds the key parameter usage and a motivational scenario. Every sentence earns its place with 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?
Given the tool has only one optional parameter and no output schema, the description covers the essential aspects: what it does, how the parameter works, and when to use it. It does not explain the return format in detail, but for a simple list operation this is sufficient.
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 for the single parameter is 100%, so baseline is 3. The description adds meaningful context by explaining the real-world purpose of external_ref: 'fetch the specific bucket you created earlier under that name' and 're-anchor after losing the conversation,' which enriches the schema's terse description.
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 clearly states the tool's purpose: 'List your webhook endpoints.' It also explains a secondary behavior with external_ref to fetch a specific bucket. However, it does not explicitly distinguish from sibling get_bucket, so it is clear but not fully differentiated.
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?
The description provides a concrete use case: 'Pass external_ref to fetch the specific bucket you created earlier under that name — this is how you re-anchor after losing the conversation.' This gives clear when-to-use context. It does not mention alternatives or exclusions, but the scenario is explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: buckets, events, schemas, deliveries, forwarding, verification, replay, and waiting. Even similar pairs like latest_event vs list_events are clearly differentiated by purpose, with no overlapping responsibilities.
Most tools follow a consistent verb_noun pattern with underscores, such as create_bucket, list_events, and delete_bucket. The only slight deviation is 'latest_event', which uses an adjective instead of a verb, but it remains intuitive and does not disrupt the overall predictability.
At 17 tools, the set is slightly above the typical well-scoped range of 3-15, but the domain covers buckets, events, schemas, deliveries, configuration, and more, so each tool serves a distinct and justified purpose. The count feels appropriate for the platform's breadth rather than excessive.
The set covers the primary lifecycle for buckets, events, and schemas, including create, read, list, and delete operations. However, there is no way to update or delete a forwarding rule after creation, and no explicit update operation for bucket metadata, leaving notable gaps in managing configurations.
