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

The description discloses the critical non-obvious behavior that the tool 'opens nothing by itself' and returns a step-by-step procedure, which the annotations (readOnlyHint, destructiveHint=false) do not convey. It also notes there is no official MCP server, explaining why the browser fallback exists. It stops short of describing output format details or any auth/session requirements for the subsequent browser calls.

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 'from ChatGPT, Claude or any AI agent' is marketing framing rather than tool semantics, and the trailing API note repeats 'Acuity Scheduling' twice in a redundant construction. The most important fact — that the call returns instructions and performs no action — is buried mid-sentence instead of front-loaded.

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?

For a zero-parameter, read-only tool with no output schema, the description should make the return value unambiguous; it partially does by naming 'screens, buttons, fields', but leaves open whether actual appointment records are ever surfaced. The hand-off to cotlet_browser_* is covered, but the workflow's end state is not fully spelled out.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema's empty object with additionalProperties=false is consistent with the description's framing of a no-input instructional call.

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 name and title say 'list appointments', but the description reveals the tool does not list anything itself — it 'Returns how to do it in Acuity Scheduling step by step (screens, buttons, fields) and opens nothing by itself.' That is a guide/instruction tool, not a data-fetching one, so an agent reading the first sentence would form the wrong expectation. The actual purpose is only discoverable after reading the second clause.

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?

It gives one concrete usage instruction: after getting the steps, execute them 'with the cotlet_browser_* tools in the user's Acuity Scheduling Cloud Browser.' It does not say when to prefer this over siblings like acuity_scheduling_check_availability or acuity_scheduling_book_appointment, nor does it state any preconditions or exclusions.

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