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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: group chat invite links and contacts are deliberately excluded and only appear on the community's page, so the agent knows not to expect them. It doesn't discuss pagination or error behavior, but for this tool that's minor.

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 sentences, zero filler. The positive scope comes first, then the prerequisite, then the negative scope — all front-loaded and each sentence carrying distinct 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?

With no output schema, the description compensates by enumerating the returned fields and explicitly noting what is absent, which is exactly what an agent needs to decide whether this tool answers its question. Nothing required to call it correctly is missing.

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?

Schema coverage is 100% and the single `slug` parameter is already documented as coming from search_communities, so the description repeats rather than extends the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Get one local community's public details') and then enumerates the payload — operations, location, languages, people, venues, events — which pins down exactly what this tool returns versus get_event/get_teacher/get_venue. An agent can distinguish it from the search_*/get_* siblings 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?

Explicitly states the prerequisite and the source of the identifier: 'Use with a slug from search_communities,' which routes the agent through the correct lookup tool first. It stops short of naming when-not to use it (e.g., when you don't yet have a slug), so it's clear guidance without full exclusion criteria.

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