kadam_adv_create_audience

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

Discloses type-specific behavioral requirements and limitations (e.g., createFingerprint only valid for certain types), adding value beyond the readOnlyHint annotation. Lacks details on authentication or error conditions.

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?

Efficiently structured with a clear purpose statement followed by type-specific details in a compact, bullet-like format. No redundant information.

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?

Covers all primary use cases and required parameter combinations for creating different audience types. Could benefit from mentioning potential error scenarios or idempotency, but sufficient for agent invocation given the absence of output schema.

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?

Adds meaningful context by grouping parameters by audience type and explaining conditional dependencies (e.g., campaignIds required for type=audience, at least one boolean tracking field). This supplements the schema's 70% 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 explicitly states 'Create a new audience' and breaks down into types, clearly distinguishing this tool from sibling tools that create other entities (e.g., campaigns, creatives).

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?

Provides clear guidance on required fields per audience type and notes that fingerprint audiences cannot be created directly, but could be more explicit about when to use this tool vs. alternatives like update_audience.

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