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

No annotations are present, so the description carries the full burden of behavioral disclosure. It names the mutation ('rename' or 'change saved filter') but does not explain whether the update is a partial or full replacement, what happens to existing audience references, whether validation errors can occur, or what the response looks like. This is a meaningful gap for a mutation tool.

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 description is a single efficient sentence with no filler. It clearly lists the two supported update operations and is easy to parse.

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?

Given no output schema and no annotations, the description is too thin for a mutation tool with a nested filter object. It omits usage context, side-effect transparency, and any indication of success or failure behavior, so an agent gets only the bare minimum needed to understand the action.

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%: name, filter, organization_id, and audience_id all have descriptions. The tool description adds no significant parameter semantics beyond what the schema already provides, so the baseline of 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 states a specific verb and resource: rename an audience or change its saved filter. It clearly distinguishes this tool from siblings like create, delete, get, and member operations, so an agent can identify what it does at a glance.

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 is implied by the description—modify an existing audience's name or filter—but there is no explicit guidance about when to use this tool versus alternatives like commsharbor_audience_create or commsharbor_audience_delete. No exclusions or alternative recommendations are provided.

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