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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses only the core mutation (adding a member) but does not state what happens when the contact is already a member, whether dynamic audience IDs are rejected, what error conditions apply, or what the result confirms. A mutation tool with zero annotation coverage needs more behavioral context than this.

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?

A single nine-word sentence with the action verb front-loaded. Every word earns its place, and there is no duplication of schema content or filler material.

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 three-parameter mutation with fully described required parameters, the core is adequately covered. However, with no output schema, the description does not indicate what the call returns on success, how duplicate membership is handled, or whether the static-audience constraint is enforced — gaps an agent needs to know whether re-adding is safe or how to confirm the operation succeeded.

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%, with each parameter already described ('CRM contact ID', 'Audience ID', 'Active organization ID'). The description slightly enriches contact_id (must be a CRM contact) and audience_id (must be static) but adds no syntax, format, or relationship details beyond the schema, so the 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 uses a specific verb+resource pair: 'Add a CRM contact to a static audience.' It is readily distinguishable from siblings like commsharbor_audience_member_remove (opposite action) and commsharbor_audience_create (different resource). The 'static audience' qualifier adds precision beyond what the tool name alone conveys.

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?

The intended action is evident from the verb, but there is no explicit when-to-use or when-not-to-use guidance. It does not distinguish this tool from bulk import workflows (commsharbor_contact_import_*) that could also populate audiences, nor does it state what to do when the audience is dynamic. The 'static audience' phrase is an implied usage condition, but no alternative tool is named.

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