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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description adds the endpoint path and the shape of a returned group, which is modest extra context, but says nothing about pagination behavior, result limits, or whether the default view filters anything out.

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 preamble, with the core action and its domain synonyms front-loaded before the endpoint footnote. The long parenthetical of returned fields is dense but scannable. Structurally efficient; nothing is wasted, though the field list could be trimmed without much loss.

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 usefully compensates by naming the fields a group contains, and every one of the nine optional filters is fully documented in the schema. Combined with annotations that carry the read-only/idempotent profile, an agent has enough to call this correctly; only return-envelope concerns like pagination metadata or empty-result behavior are unaddressed.

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 description coverage is 89%, so the schema already documents q, days, page, view, order_by, per_page, site_ids and cluster_ids in detail; the description adds no parameter-level meaning on top of that. The parenthetical list of fields maps loosely to the frequency enum but does not explain that parameter, whose schema entry has no description at all.

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+resource ("List small groups") and disambiguates the domain by naming synonyms ("home groups/life groups"), plus the underlying endpoint GET /smallgroups/groups. It also enumerates the fields each group carries, so an agent knows exactly what a result represents. It stops short of explicitly contrasting with the singular sibling churchsuite_get_small_group, which is the only remaining differentiator an agent must infer from naming.

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?

Usage is implied rather than stated: the plural resource name plus the filter set (days, view, frequency, site_ids, cluster_ids) makes it clear this is the browse/filter tool, but the description never says when to prefer it over churchsuite_get_small_group or churchsuite_list_small_group_members. No exclusions, prerequisites, or alternative routing are given.

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