Create Audience

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

With no annotations, the description carries the full burden and discloses almost nothing: not whether the new audience starts empty, whether creation is idempotent on duplicate names, what permissions are required, or what the response returns. 'for campaigns' is the only behavioral hint.

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 front-loaded sentence with no wasted words. It is efficient, though brevity here comes partly from under-specification rather than deliberate economy.

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 mutation tool with zero annotations and no output schema, the description should say what gets created and what is returned (e.g., audience ID) and whether the audience is empty. None of that is present, leaving the agent guessing at post-creation behavior.

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?

One parameter at 100% schema coverage, so the schema already defines 'name' fully; the baseline of 3 applies. The description adds no constraints such as name uniqueness, allowed characters, or default naming behavior.

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?

Specific verb (create) plus resource (audience) with a scope hint (for campaigns). An agent can distinguish it from get/list/update/delete-audience without opening schemas, though the description adds nothing beyond the title and name.

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 on when to create a new audience versus using an existing one via list-audiences/get-audience, no mention of prerequisites, uniqueness rules, or what should happen before adding contacts to it.

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