zenoti-appointments-list

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

No annotations provided; description only says 'list' with 'filtering options'. It does not disclose read-only nature, pagination, sorting, side effects, or any behavioral traits. The description carries the full burden but fails to provide meaningful transparency.

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?

Very short single sentence, but it is not efficiently informative. It lacks structured details about parameters, usage, or output. Concise but at the expense of completeness.

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 7 parameters, 2 required, and no output schema, the description is completely inadequate. It does not specify output format, pagination behavior, required parameter constraints, or how the filtering works. The agent cannot correctly invoke the tool based on this description alone.

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 0% and the description does not explain any parameters. The phrase 'filtering options' is vague; no details on center_id, date, status, guest_id, therapist_id, page, size, or how to use them. The description adds no value beyond the schema.

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 appointments with filtering options. It uses specific verb 'List' and resource 'appointments', and distinguishes from siblings like 'get' (single) and actions like 'checkin' or 'noshow'.

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. Siblings include other appointment listers or action tools, but the description does not help differentiate or provide context for when to use filtering vs other endpoints.

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