eb_org_webhooks

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

Read-only annotation is present and aligns with the description. The description adds the behavioral detail that it returns webhooks and their subscribed actions, which is useful since there is no output schema. It does not contradict 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?

A single, clear sentence with no wasted words. The verb is front-loaded and the structure is optimal for quick comprehension.

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 simple read-only list operation, the combination of description, schema, and annotations is adequate. The description covers return content, the schema covers parameters, and the annotation covers safety. Slight gap: no mention of pagination in description, but the continuation token in the schema implies it.

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% (both org_id and continuation have descriptions). The tool description does not add any parameter-specific meaning beyond what the schema already provides, so baseline 3 applies.

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 lists an organization's registered webhooks and the actions they subscribe to. The verb 'List' is specific, the resource is well-defined, and it distinguishes from sibling tools like eb_org_events or eb_org_orders.

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?

No guidance is provided on when to use this tool vs alternatives. It only says what it does, with no mention of alternatives, exclusions, or prerequisites. Usage context is entirely implied.

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