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

With only destructiveHint=true in annotations, the description adds the useful clarification that this creates a membership rather than altering the group itself. However, it omits whether the call is idempotent when the contact is already a member, what permissions are required, and why the operation is flagged destructive.

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 sentences with the action and the key selection rule front-loaded; the trailing 'LACRM: CreateGroupMembership' tag is metadata that does not impede reading. Little waste overall.

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 simple 3-parameter mutation with full schema coverage and no output schema, the description covers the essentials (action, effect, group identification). It is still thin on duplicate handling, permissions, and post-call state, which matters for a write operation with minimal annotations.

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 real value beyond the schema: the mutual-exclusion rule ('group_id ... or group_name — not both') and the explicit preference order for identifying the group, which the schema does not express.

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 gives a specific verb and resource ('Add a contact or company to a group') and clarifies the underlying effect ('creates a group membership'). This cleanly distinguishes it from siblings like lacrm_list_contacts_in_group and the various lacrm_create_* tools.

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?

It tells the agent how to identify the group (group_id preferred, or group_name, not both), which is useful routing guidance, but never states when to use this tool versus alternatives or any exclusions such as whether the contact must already exist.

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