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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the exact returned scope (organizer/co-organizer only), the fields exposed (member count, your role), and an auth requirement tied to the app. No mention of pagination or rate limits, which keeps it from a 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?

Three short sentences, front-loaded with the scope and followed by the chaining instruction and auth note. Slight redundancy: 'Groups you organize or co-organize' and 'Returns every group where you are organizer or co-organizer' restate the same constraint, costing a sentence of economy.

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 input parameters, no output schema, and annotations already covering the read-only safety profile, the remaining burden falls on return content and usage. The description covers both: it lists the key returned fields (member count, role, group_urlname) and explains how the identifier is consumed by sibling tools.

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 per the rubric. The description cannot add parameter meaning, and it correctly focuses instead on the return payload and how to feed group_urlname into downstream calls.

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 with an explicit scope: only groups where the user is organizer or co-organizer. That scoping sharply distinguishes it from the other meetup list tools (list_events, list_members, list_attendees). An agent knows exactly what comes back without opening a schema.

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?

Gives an explicit downstream instruction: use group_urlname from each item as the group parameter of the other tools, positioning this as the entry point for the meetup tool family. It also names the prerequisite (Cotlet API key with access to this app). It does not state when-not to use it, but there is no competing sibling for listing groups, so the guidance is effectively complete.

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