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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds the non-obvious fact that the tool performs no action and must be paired with browser tools. The note on PatientNow's official REST API and gateway-key requirement explains why the browser route is used, though it is more justification than operational detail.

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 key behavior (returns instructions, does not act) is front-loaded in the first two sentences, which is good. The third sentence about PatientNow's REST API and a gateway key is a digression with marketing-style phrasing ('from ChatGPT, Claude or any AI agent') that dilutes the operational content.

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 parameters and no output schema, the description carries the burden of describing the return value, and it does so concretely (screens, buttons, fields). The remaining gap is that with zero inputs it never explains how the agent should indicate which appointment to reschedule, leaving the caller to infer the tool returns generic guidance.

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 the baseline is 4 and there is nothing for the description to disambiguate. It could still clarify how the target appointment is identified given the empty schema, but that is a contextual rather than a parameter-semantics gap.

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 verb and resource (reschedule an appointment in PatientNow) and immediately corrects the naive reading by stating it returns step-by-step instructions rather than performing the action. It does not explicitly differentiate itself from the sibling patientnow_book_appointment, which likely has the same instruction-returning shape.

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 an explicit workflow: call this to get the screens/buttons/fields, then execute with cotlet_browser_* in the PatientNow Cloud Browser, and states it opens nothing by itself. It stops short of saying when to prefer this over the booking sibling or what to do if the user has no Cloud Browser session.

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