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

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotent, closed-world), and the description adds meaningful context beyond them: the tool 'opens nothing by itself', returns screens/buttons/fields guidance, and requires a follow-up browser session. That clarifies the read-only claim and the two-step handoff. It does not describe output shape or whether the steps are guaranteed current, which keeps it below 5.

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 content is front-loaded with the purpose and the handoff, which is good, but the second and third sentences are long run-ons that pack instructions, disclaimers and a dated API note into one breath. The 'checked 9 Nov 2026' parenthetical is a digression that consumes space without helping the agent decide or call. It is serviceable but not tight.

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 guidance tool, the description supplies what an agent needs: what it returns (step-by-step screens, buttons, fields), what it does not do (opens nothing), and which tools to use next. The remaining gap is that it does not state whether the returned steps are authoritative or how to report stale instructions, but the essential picture is complete.

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 are no parameter semantics to explain and the baseline of 4 applies. The description correctly introduces no parameter discussion, and additionalProperties=false is consistent with a no-argument call.

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 opens with a specific verb and resource: 'List memberships in the user's own Moxie account'. It then clarifies that the tool actually returns step-by-step instructions rather than the membership data itself, which resolves what would otherwise be a mismatch with the name. It does not explicitly contrast itself with the sibling moxie_list_clients, so sibling differentiation is implied only by the resource noun.

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 states the workflow clearly: call this to get the steps, then execute them with the cotlet_browser_* tools. It also rules out an alternative approach by noting Moxie publishes no API, webhooks or Zapier app, so the agent knows not to look for a direct integration. It does not say when to prefer this over cotlet_app_guide for the same information.

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