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, and 'Delete an audience' does not carry it. It confirms the destructive nature honestly, but reveals nothing about irreversibility, cascading effects on audience members, permission requirements, or the expected response. The word 'delete' prevents a score of 1, but the burden is otherwise unmet.

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?

The three-word sentence has zero waste, but the brevity reflects under-specification rather than disciplined editing. For a destructive operation with no annotations and no output schema, a single clause is not an appropriately sized description.

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 and no annotations, the description must carry the contextual load, and it does not. For a destructive tool with a closely related sibling (commsharbor_audience_member_remove), an agent needs to know whether deleting an audience also removes its members, whether the action is reversible, and what outcome to expect. All of this is missing.

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 both audience_id and organization_id already described in the input schema ('Audience ID' and 'Active organization ID'). The description adds nothing about parameters, so the baseline of 3 is appropriate — the schema does the heavy lifting.

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 states a specific verb ('Delete') and resource ('an audience'), and the destructive verb clearly differentiates it from sibling tools like commsharbor_audience_create, commsharbor_audience_get, and commsharbor_audience_update. However, it essentially restates what the tool name already implies, adding no detail about scope or operation semantics.

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?

No guidance is provided on when to use this tool versus alternatives. In particular, an agent gets no help distinguishing it from commsharbor_audience_member_remove (removing individual members) or commsharbor_audience_update (modifying an audience instead of destroying it). No conditions, prerequisites, or exclusions are stated.

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