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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description adds the mutual-exclusivity constraint and the preference ordering of the two identifiers, which is useful. It does not disclose pagination behavior or the shape of the returned contact list, but with annotations carrying safety that gap is minor.

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, front-loaded with the action and scope, followed by the identifier rule. No filler, and the trailing 'LACRM: GetContactsInGroup' is a compact upstream-method anchor.

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 read-only, fully schema-documented list tool with no output schema, the description covers selection and identifier semantics adequately. It could still note that results are paged (relevant given the page/max_results params) and roughly what a result row looks like, which is the only real gap.

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 the baseline is 3, but the description adds genuine value the schema does not: that group_id and group_name are mutually exclusive and that group_id is preferred. The schema alone only hints at preference via 'if you do not have its id' and never states the exclusivity rule.

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 precise verb and resource with scope: 'List the contacts that are members of one group.' This is meaningfully narrower than lacrm_search_contacts or lacrm_get_contact_groups, so an agent can place it correctly. It stops short of a 5 because it never names the sibling it is not (e.g., search_contacts), leaving the differentiation to inference.

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 context is implied by the scope ('members of one group') but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., use search_contacts for cross-group queries). The 'group_id (preferred) or group_name — not both' note is really parameter guidance rather than tool-selection guidance.

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