create_audience

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only repeats the create action and mentions 'contact info and campaign defaults', but does not disclose side effects, permissions, error conditions, or return value. This is insufficient 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, concise sentence that is front-loaded with the action ('Create a new audience/list') and contains no extraneous information. It is appropriately sized and 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?

With 12 required parameters, no annotations, and no output schema, a one-sentence description is not complete. It does not mention what the tool returns, any prerequisites, or potential failure states. The schema covers parameter definitions, but the description fails to provide broader operational context.

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?

All 12 parameters have detailed descriptions in the input schema (100% coverage), so the description adds no additional parameter-level meaning. The phrase 'contact info and campaign defaults' groups some parameters but does not explain them beyond the schema.

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 clearly states the tool's function: 'Create a new audience/list with contact info and campaign defaults'. It uses the verb 'Create', identifies the resource as 'audience/list', and adds scope ('contact info and campaign defaults'). This distinguishes it from sibling tools like update_audience and delete_audience.

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 implies usage for creating a new audience, but it does not explicitly state when to use this tool over alternatives or provide any exclusions. No reference is made to sibling tools, so the agent must infer usage from the tool name and sibling list.

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