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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), the description adds the critical behavioral fact that the tool 'opens nothing by itself' and only returns an instructional result, which prevents an agent from assuming a side effect occurred. It also discloses the sourcing/verification context for the no-API claim. It does not describe the return payload's shape or size, but for a zero-parameter guide tool the key behavior is covered.

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 core routing information is front-loaded and efficient, but the trailing citation about the pricing page and the '(checked 9 Nov 2026)' dating reads as justification boilerplate that does not help an agent call the tool. The single long run-on sentence bundling purpose, behavior, next step, and API status reduces scannability.

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, no-output-schema tool, the description covers what is returned (step-by-step screens, buttons, fields), that no action is taken, and what to do next. The remaining gap is the exact format of the returned guide, which is modest given the tool's simplicity.

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; the baseline for a 0-param schema applies. The description correctly implies no input is needed and instead frames the output as the actionable artifact.

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 names a specific resource (appointments in the user's Klean CRM account) and explicitly states what the tool actually returns: 'how to do it in Klean CRM step by step (screens, buttons, fields)'. However, the opening verb 'List appointments' is in tension with the clarification that it 'opens nothing by itself', so an agent skimming the first clause could expect data rather than instructions. It does partially differentiate by pointing to the cotlet_browser_* family for the actual work.

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 a clear sequencing rule: call this to get the steps, then execute them with the cotlet_browser_* tools in the Klean CRM Cloud Browser. The note that Klean CRM has no official API, webhooks, or Zapier app explains why the browser route is the only option and implicitly rules out an API-based approach. It stops short of naming when to prefer a different guide-style sibling such as cotlet_app_guide.

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