create_interest_category

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

With no annotations, description fully handles behavioral disclosure: mentions authentication via API key, Mailchimp rate limits (max 10 concurrent requests), and support for read-only/dry-run modes. Lacks clarity on duplicate title handling but otherwise comprehensive.

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?

Well-structured with sections (purpose, workflow, auth, args, returns, example). Each sentence adds value. Slightly verbose in documenting Args (which could be implicitly understood from schema), but not overly so.

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?

Given 3 required params and no annotations, the description fully equips the agent: explains workflow, parameter constraints, return fields, and an example. Output schema exists, so return structure is clear. No gaps for correct invocation.

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 0%, but description adds significant meaning: explains list_id source ('Obtain from list_audiences'), title uniqueness requirement, and valid type values ('checkboxes', 'dropdown', 'radio', 'hidden') with interactive behavior. Example further clarifies usage.

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?

Clearly states it creates an interest category (group container) in an audience. The description differentiates from sibling 'create_interest' by explicitly outlining the typical workflow: create_interest_category -> create_interest.

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 explicit when-to-use ('container for interest options'), workflow steps ('create_interest_category -> create_interest'), and recommends listing existing categories first via 'list_interest_categories'. No negative guidance needed.

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