Call first for step-by-step guidance on creating or copying Meetup events, including screens and sign-in link.
How to work in Meetup (create and copy events): its screens and the sign-in link. Call this first.
| Name | Required | Description | Default |
|---|---|---|---|
| task | No | What you want done in Meetup, in your words. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It implies a read-only informational tool and lists what the guidance covers (screens, sign-in link), but never states that it has no side effects, what form the guidance takes, or whether every task requires calling it.
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?
Two short clauses, with the scope front-loaded and the imperative 'call this first' placed last for emphasis. Nothing redundant.
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 simple guidance tool with one optional string parameter and no output schema, the description is close to sufficient. The remaining gap is what the response looks like and whether guidance must be re-fetched per task.
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?
One optional parameter with 100% schema description coverage, so the schema already explains 'task'. The description adds no format, granularity, or example hints beyond that, which is the baseline for fully covered parameters.
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 that this returns guidance on working in Meetup, scoped to creating and copying events, covering screens and the sign-in link. That distinguishes it from the low-level action siblings (open/click/type/read), though 'guide' leaves mildly unclear whether it returns documentation or a plan.
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?
'Call this first' gives explicit sequencing guidance relative to the sibling action tools. It does not state when it is unnecessary (e.g., if the screens are already known) or name a cheaper alternative, so it stops short of full when/when-not coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.