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

The annotations already declare readOnly, idempotent, non-destructive, closed-world, and the description stays consistent with them while adding real value: this is a guide-returning tool, not an executor, and it requires a subsequent browser session to accomplish the task. The dated note on Zen Planner's partner-only API is useful operational context. It omits whether a Cloud Browser session must already be open or what the guide output format is.

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 opening clause ('from ChatGPT, Claude or any AI agent') restates the title and adds marketing filler rather than decision-relevant information. The core mechanic is front-loaded well, but the API/partner sentence is long and its relevance is only implied. The single compound sentence with a semicolon is denser than it needs to be.

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 ('step by step (screens, buttons, fields)'). It also names the downstream tools needed to actually complete the task. Minor gaps remain around preconditions for the browser session and exact output shape.

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 nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description adds no parameter-level claims, which is appropriate 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 states a concrete deliverable: it returns step-by-step instructions (screens, buttons, fields) for listing members in Zen Planner, and explicitly says it 'opens nothing by itself.' That corrects the potential misreading of the name 'list_members' as a data-returning tool. It does not contrast itself against near siblings such as cotlet_app_guide or zen_planner_list_failed_payments, so differentiation is only partial.

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 follow-up path: after getting the guide, perform the action with the cotlet_browser_* tools in the user's Zen Planner Cloud Browser. The API note ('only for partners... contact your Daxko sales representative') effectively explains why the browser route is the one to take. It stops short of stating when to prefer a different guide or listing tool instead.

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