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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the read operation 'List' and does not mention pagination behavior (despite cursor/limit parameters), result ordering, or the distinction between static audiences and saved segments. This leaves significant behavioral traits undisclosed.

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, front-loaded sentence with no filler. It efficiently communicates the core action and resource, fitting the minimal structure expected for a simple list tool.

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?

The tool has a fully documented schema and no output schema, so the description need not explain return values. However, it does not clarify what differentiates 'static audiences' from 'saved segments' or explicitly note the paginated nature of the response, leaving some context for the agent to infer from the parameters.

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%, so all parameters (organization_id, limit, cursor) are documented. The description adds no additional parameter-level meaning, such as how 'static audiences' relates to the query or when to use cursor. Baseline 3 is appropriate given the high schema coverage.

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 'List static audiences and saved segments' clearly specifies the verb (list) and resource (audiences and saved segments). It distinguishes this from sibling tools like commsharbor_audience_get (singular fetch) and commsharbor_audience_members (list members), though it does not explicitly name them.

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 use case is implied by the verb 'List' – use this to retrieve a collection of audiences. However, there is no explicit guidance on when to choose this over siblings, such as commsharbor_audience_get for a single audience, or mention of prerequisites beyond the required organization_id.

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