zenoti-services-list

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

Description provides no behavioral details beyond the action. No annotations exist, so the description carries full burden. It does not state whether the operation is read-only, safe, or has side effects. A listing tool is likely read-only, but this is not explicit.

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 (two words) but omits critical information. While brevity is valued, it should be balanced with completeness. This is under-specified rather than efficiently written.

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 lack of output schema, annotations, and parameter descriptions, the description is completely inadequate. It fails to explain return values, pagination, filtering, or any other behavioral context that an agent needs to use the tool correctly.

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?

Input schema has two parameters (center_id required, category_id optional) with no descriptions. Schema description coverage is 0%, and the description adds no meaning about these parameters. An agent gets no guidance on what values to provide or how they affect results.

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?

Description states 'List services', which indicates the tool's action and resource, but lacks specificity about what services and in what context. It distinguishes from sibling 'zenoti-services-get' which retrieves a single service, but does not clarify scope (e.g., by center or category).

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 like 'zenoti-services-get' or 'zenoti-therapists-list'. The description does not mention any prerequisites or context for use.

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