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

With no annotations, this description carries the full burden of communicating behavior. It makes clear that the operation is a read-only listing and that saved segments are included, but it does not describe pagination behavior, response shape, or any operational boundaries beyond what the schema implies.

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 sentence with no filler and names exactly what the tool returns. It is front-loaded and every word adds meaning.

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 list operation this is minimally adequate, but there are gaps: no output schema and no annotations exist, and the description does not mention pagination, the response format, or how this relates to sibling audience tools. The schema covers parameters, but the overall context is thin.

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?

The input schema already fully describes all three parameters (organization_id, limit, cursor) with 100% coverage, so the description adds no parameter-level meaning. This is the appropriate baseline for 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 uses a specific verb ('List') and names the resources ('audiences and saved segments'), so an agent can tell this is a collection-list operation rather than a single-item get/create/update. It is distinguishable from related siblings like commsharbor_audience_get, though it does not explicitly name an alternative.

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 description gives no guidance about when to choose this tool over the related audience tools, and it mentions no exclusions or alternative tools. An agent must infer the use case solely from the word 'List', which is minimal guidance.

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