zenoti-booking-reserve

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it says nothing about side effects, state changes, cancellations, or error conditions. The tool is likely a write operation, but that is not indicated.

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?

While extremely concise at 3 words, the description is under-specified for a tool with 5 required parameters and no schema descriptions. Conciseness should serve completeness, not replace it.

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's complexity (5 params, no output schema, no annotations), the description fails to provide minimally sufficient context for correct invocation, such as behavior or 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?

The input schema has 5 required parameters with no descriptions (0% coverage), and the description does not explain any parameter meaning, leaving the agent to guess what 'center_id', 'slot_time', etc., represent.

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 'Reserve a slot' is vague; it states a verb and resource but doesn't specify what type of slot (e.g., appointment, service), and it fails to differentiate from sibling tools like 'zenoti-booking-confirm' or 'zenoti-availability-slots'.

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. The sibling 'zenoti-booking-confirm' suggests 'reserve' might be a preliminary step, but no context is given, leaving the agent without decision support.

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