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

With readOnlyHint and openWorldHint already covering safety, the description adds real value: it enumerates returned fields, decodes the status codes (a/o/e), and explains pagination and count_only response shapes. It doesn't mention rate limits or ordering, but the behavioral disclosure is well above the annotation baseline.

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 tight sentences, front-loaded with the core purpose, then paging and the count_only variant. No filler or redundancy.

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?

No output schema exists, so listing the returned fields and status codes is essential and done well. The archived-member toggles are covered by the schema rather than the description, which is acceptable given 100% coverage, but a brief note on deleted handling would have made it fully self-contained.

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%, so every parameter is already documented in the schema. The description reinforces next_start and count_only semantics but adds little beyond that, leaving deleted_only, include_deleted, and exclude_fields solely to the schema. Baseline 3 is appropriate.

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 the members (contacts)') and scopes it to 'the whole audience', which implicitly distinguishes it from group- or search-scoped siblings like emma_list_group_members and emma_get_search_members. It stops short of naming those alternatives explicitly, so differentiation is inferable rather than spelled out.

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 operational guidance for paging ('use next_start for more') and for count_only, but never states when to choose this tool over siblings such as emma_list_group_members, emma_get_search_members, or emma_find_member_by_email. Usage is implied by the 'whole audience' scope rather than stated.

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