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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and the description is consistent with them, reinforcing that it 'opens nothing by itself.' It adds useful context beyond the annotations: the output is a step-by-step procedure and the actual mutation must be done via browser tools. It does not describe the shape or length of the returned instructions.

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 message is front-loaded, but the trailing note about Zendesk's REST API and 'no documented Zendesk-hosted MCP server (checked 16 Oct 2026)' is tangential and does not help an agent decide or invoke. The lead sentence also misdirects before self-correcting, costing clarity.

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 guide tool, the description covers what it returns (step-by-step screens/buttons/fields) and how to act on it (browser tools). It is nearly complete, though it could say more about what the returned instructions look like or any prerequisites for the browser session.

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 no parameter semantics to explain and the baseline of 4 applies. The description does not need to compensate for any schema 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 opening clause 'Update ticket in the user's own Zendesk account' names a verb and resource, but the tool does not actually update anything; the second clause ('Returns how to do it in Zendesk step by step... opens nothing by itself') corrects the framing. The real purpose (produce step-by-step instructions) is only clear after reading past the misleading lead, and it is not sharply distinguished from siblings like zendesk_reply_to_ticket or zendesk_apply_macro.

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 explicitly routes the agent: use this to get the procedure, then perform it with the cotlet_browser_* tools in the user's Zendesk Cloud Browser. That is a concrete when-to-use and a named alternative path. It stops short of stating when NOT to use it (e.g., versus zendesk_apply_macro for bulk changes).

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