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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds useful domain context by explaining that groups come in static, smart, and mailing-list flavors, but says nothing about result-set shape, ordering, or the default exclusion of inactive groups beyond what the schema states.

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 compact fragments with the entity definition front-loaded and no filler. The trailing 'APIv4 Group.get' is terse and marginally useful for technical callers, though it slightly crowds out the usage guidance that is missing.

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 low-complexity, read-only list tool with full schema coverage and safety annotations, the description is largely sufficient: it defines the entity, enumerates representative returned fields in the absence of an output schema, and points at the underlying API. The remaining gap is that it doesn't clarify group-vs-group-membership selection against civicrm_list_group_contacts.

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 100%, and the schema fully documents limit, offset (including the next_offset handoff), title filter, and the active_only default. The description's mention of title/description/visibility/type refers to returned fields, not parameters, so it adds no semantic depth to the four inputs. 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?

The description names the resource (contact groups) and disambiguates the entity with concrete domain vocabulary — mailing lists, static groups, smart groups — plus the fields surfaced. It never names the closest sibling (civicrm_list_group_contacts), so the agent must infer the groups-vs-group-members distinction on its own.

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?

There is no statement of when to reach for this tool, no prerequisites, and no alternatives offered — neither civicrm_list_group_contacts nor civicrm_query is mentioned as an option. The 'APIv4 Group.get' suffix is an implementation reference, not usage guidance.

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