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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the underlying API endpoint (GET /smallgroups/members) but says nothing about pagination limits or auth, so it is only marginally additive beyond the annotations.

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?

Three compact sentences: purpose and return fields first, then filter routing, then API endpoint. No filler, and the most decision-relevant information is front-loaded.

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 enumerates the returned fields and explains filter modes, which is what an agent needs to call this correctly. Pagination is covered by schema descriptions, so nothing critical is missing, though response shape is only sketched.

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 88%, so per-parameter docs largely exist. However, the description adds non-obvious filter semantics: group_ids returns a group's members while contact_ids/child_ids return a person's groups — a dual-mode behavior not evident from the schemas alone. The status/role_id filters are left to the schema.

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 ('List small group memberships') and enumerates the returned fields (group id, person = contact or child id, status, role ids, joined date). This clearly separates it from siblings like list_small_groups or list_ministry_members, which cover different entities.

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 explicit routing: filter by group for a group's members, by contact/child for a person's groups, and points to get_contact/get_child for id lookup. It lacks any 'when not to use' or exclusion guidance, but the bidirectional filter guidance is strong.

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