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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context: what is listed (discoverable communities), what is never listed (private family rooms), and that join mode (open or by request) and next gathering are surfaced.

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?

Front-loaded with the scope and exclusion, followed by the usage trigger; no filler sentences. The opening sentence is dense with several clauses, but each carries distinct information (subtypes, join mode, gathering, family-room exclusion).

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 an output schema present, return-value explanation is unnecessary, and the description covers scope, exclusions, and join semantics well. The remaining gap is pagination/limit behavior for a paged, cursor-based tool, which neither description nor limit param documents.

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 67% – the query and cursor params carry descriptions, but limit (default 10, max 20) is undocumented in both schema and description. The description adds no syntax or format guidance beyond the schema's examples ('prayer', 'study', 'Atlanta'), so the baseline 3 applies.

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 resource ('discoverable communities on The Living Bread a person can join today') plus the concrete subtypes returned (prayer groups, study groups, city/interest communities), and explicitly excludes private family rooms. An agent can distinguish it from siblings like find_gatherings_near or events_this_week without opening the 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 a clear use trigger: 'Use when someone wants people to pray or walk with, or asks "is there a prayer group".' It covers when to use but names no alternative tool or exclusion condition, so the routing versus nearby gathering/church tools is left to inference.

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