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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds genuine behavioral content beyond that: the return contains tags paired with upcoming-meetup counts, and the counts are scoped to 'upcoming' rather than all-time. There's no output schema, so this return-shape signal is doing real work.

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 sentences, with the resource and return content front-loaded before the follow-up routing hint. No filler, no restatement of the title, and nothing that could be cut without losing information.

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 parameterless list tool with no output schema, an agent needs to know what comes back and what to do next, and the description covers both. The only gap is that it doesn't say whether the list is exhaustive or how large it may be, which is minor given the closed-world annotation. Complexity is low, so the two sentences are nearly sufficient.

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 at the input layer; baseline 4 applies. The mention of a 'tag id' refers to a parameter of the sibling search_meetups, not this tool, and is correctly framed as a hand-off rather than an input 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 names the resource (topic tags) and states what each entry carries (a count of upcoming meetups), which is more specific than the bare name 'list_topics'. It doesn't use an explicit verb like 'list' or 'enumerate', but the noun phrase plus the tool name makes the operation unambiguous. It also differentiates itself from search_meetups by indicating tags feed into that tool.

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?

The sentence 'Pass a tag id to search_meetups' gives a concrete downstream use and implicitly frames this as a discovery step before searching. However, it never states when to prefer this over list_sources or list_upcoming_meetups, nor when-not to use it. Usage is implied rather than spelled out.

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