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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: the tool performs no action itself and returns a UI walkthrough, and mHelpDesk has no API/webhook/Zapier surface (syncing only with QuickBooks and Google Calendar). The dated verification note ('checked 9 Nov 2026') is odd but signals recency of the claim.

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?

Three sentences, front-loaded with the outcome and then the mechanics, with no filler. The final sentence about the absent API and QuickBooks/Calendar sync is somewhat tangential, but it preempts a plausible agent detour, so it largely earns its place.

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 guide tool with no output schema, the description covers what is returned, what it does not do, and the follow-up tool family. The one remaining gap is that it never characterizes the shape of the returned guidance (single flow vs. multiple options) or whether it depends on the user already being logged into the Cloud Browser.

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 compensate for. The empty schema is consistent with a fixed 'how do I list customers' guide response, and the description does not need to explain arguments.

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 states a specific verb and resource ('List customers in the user's own mHelpDesk account') and, crucially, corrects a likely misreading of the name: it returns step-by-step instructions rather than customer records, and opens nothing by itself. An agent can tell immediately what it gets back and how it differs from the mhelpdesk_create_* siblings.

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 clear sequencing guidance: call this to get the screens/buttons/fields, then execute the flow with the cotlet_browser_* tools in the mHelpDesk Cloud Browser. It also explains why no API route exists (no public API, webhooks or Zapier app), which forecloses an alternative an agent might otherwise reach for. It stops short of naming cotlet_app_guide or stating conditions under which this tool is unnecessary.

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