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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real context beyond them: results are returned in the account time zone, which fields come back (including a label only if one was set), and that a Cotlet API key with access is required. Return-format and pagination behavior are not addressed, but the auth and time-zone disclosure is meaningful.

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 opening clause and the second sentence overlap heavily – both enumerate customer, service, team member, and label – creating noticeable redundancy. The usage and auth notes are front-loaded usefully, but roughly a sentence of content is repeated.

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?

With no output schema, the description takes on return-value explanation and does so (fields returned, time zone, conditional label). It also covers filtering, downstream ID usage, and auth. Only pagination/volume behavior, which an agent might want for a date-range list, is unaddressed.

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 coverage is 100%, so all four parameters are already documented with format and defaults. The description adds only the framing of 'between two days' and 'filter by team member or service,' which largely restates the from/to and staff_id/service_id schema descriptions. Baseline 3 is appropriate when the schema carries the detail.

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?

States a specific verb (list) plus resource and scope: appointments in a date range, with the entity fields included and optional team member/service filters. An agent can distinguish it from get_appointment or list_available_slots by name and scope alone.

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?

Clearly signals how to use the output: 'Use appointment_id from each item in get_appointment, reschedule_appointment and cancel_appointment,' which routes the agent to the correct follow-up siblings. It does not, however, explicitly state when to prefer this list over get_appointment or get_appointment_report, so the boundary with those siblings is left to inference.

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