zenoti-webhooks-subscribe

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

No annotations are present, and the description does not disclose any behavioral traits such as what happens upon subscription, whether the callback URL is validated, potential side effects, or error conditions. For a non-read-only tool, this is a significant gap.

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 extremely concise (3 words), but it sacrifices completeness for brevity. While front-loaded, it does not earn its place as it fails to provide sufficient information for tool selection and use.

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 2 required parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain the subscription process, event types, callback URL format, or any operational details necessary for correct usage.

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?

The description adds no meaning beyond the schema's property names and types. Schema description coverage is 0%, meaning parameters like 'event_type' and 'callback_url' are unexplained. The enum values are listed but not described, offering no insight into their significance.

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 'Subscribe to webhooks' clearly states the verb (Subscribe) and resource (webhooks), distinguishing it from sibling tools which are all about appointments, guests, invoices, etc. However, it could be more specific about what subscribing entails.

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 versus alternatives, prerequisites, or situations where it should not be used. The sibling tools are unrelated, so no competition, but the description offers no decision-making context.

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