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

Beyond the annotations, the description discloses two behaviors an agent could not otherwise know: the tool opens nothing by itself and it returns a procedural walkthrough (screens, buttons, fields). It also adds external access context — Meetup's GraphQL API requires an active Pro subscription and lapses with it — which explains why a browser-driving approach is used. What is missing is any statement about which event is copied or how that target is identified.

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 behavior is front-loaded in the first sentence, but it is padded with promotional phrasing ("from ChatGPT, Claude or any AI agent") and closes with a long API-availability aside carrying a check date. The API sentence does justify the tool's existence but occupies roughly a third of the text for indirect benefit.

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 explaining the return value, and it does so concretely (step-by-step screens, buttons, fields) while naming the follow-up tools needed to complete the task. The remaining gap is the missing explanation of how the source event is specified, which matters for a copy operation.

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, which normally earns a 4 baseline, but the description never explains how the event to copy is identified in the absence of an event ID or URL argument. An agent is left guessing whether the target comes from conversation context or is resolved later via the browser tools, which is a meaningful semantic 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?

States a specific verb and resource ("Copy event in the user's own Meetup account") and immediately qualifies it with the actual behavior: it returns step-by-step instructions rather than copying anything. That qualification is essential because the name alone implies an action, and the description resolves the ambiguity. It also distinguishes itself from the cotlet_browser_* siblings by naming them as the tools that actually perform the work.

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?

Usage is implied through sequencing: call this to get instructions, then execute them with the cotlet_browser_* tools in the Meetup Cloud Browser. There is no explicit when-not guidance and no comparison against the obvious sibling meetup_create_event, so an agent must infer whether to copy an existing event or create a new one.

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