zenoti-booking-confirm

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

No annotations are provided, so the description must disclose behavior. It only says 'confirm', implying a state change, but gives no details on side effects, idempotency, or error conditions. The description does not contradict annotations (none exist), but is insufficient for an agent to understand the tool's effects.

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 short (2 words), this is under-specification, not conciseness. Every sentence should earn its place, but here the single phrase provides no value beyond the tool name.

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?

Despite low complexity (2 params, no output schema), the description is completely inadequate. It fails to explain the tool's role in the booking workflow, the meaning of 'confirm', or how the parameters are used.

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?

With 0% schema description coverage, the description must explain the parameters. It does not. The 'reservation_id' and 'notes' parameters are left entirely undefined, leaving the agent to guess their purpose or format.

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 'Confirm booking' is a tautology of the tool name 'zenoti-booking-confirm'. It restates the name without adding specificity about the action or distinguishing it from sibling tools like 'zenoti-booking-reserve' or 'zenoti-appointments-*'.

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 on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., a prior reservation via 'zenoti-booking-reserve'), nor any indication of when not to use it.

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