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

Annotations already declare readOnly, non-destructive, idempotent and non-openWorld, so the safety profile is covered. The description still adds real value beyond that: it emphasizes the tool performs no action itself, describes the return content (screens, buttons, fields), and discloses the important negative fact that Moxie has no official API, webhooks, or Zapier app.

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 content is front-loaded and useful, but the prose is dense and mixes several ideas in one stream. The trailing API/Zapier disclaimer with a specific checked date is unusual framing that reads more like provenance metadata than call guidance, adding length without helping invocation.

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, no output schema and annotations already covering safety, the description does what is needed: it explains that the result is a procedural guide, names the follow-up tool family, and rules out an official API path. Minor gap is that it does not sketch what the returned steps look like or how long they are.

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; there is no parameter semantics to explain and the description neither omits nor misstates anything here.

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 gives a specific verb and resource (list clients in the user's Moxie account) and crucially clarifies that it returns a step-by-step how-to rather than the data itself. It distinguishes itself from the cotlet_browser_* family by stating it 'opens nothing by itself'. The only weakness is the tension with the name/title, which imply a data-returning list rather than an instruction-returning guide.

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 sequence: call this first to get the steps, then execute them with cotlet_browser_* tools in the Moxie Cloud Browser. However, it offers no guidance on when to prefer this over siblings like moxie_list_memberships or moxie_find_lapsed_clients, leaving the choice to be inferred from the resource names.

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