crm_create_group

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

With no annotations, the description carries the full disclosure burden and does state the create action, mandatory inputs, and returned group id. However, it does not cover prerequisites like authentication or the effect of omitting source_ai, leaving the behavioral contract only partially transparent.

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?

Three sentences pack the action, required fields, an example, optional fields, and the return-value contract with no filler. The description is front-loaded and every sentence earns its place.

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 no-output-schema creation tool, it adequately covers required inputs, an example, optional fields, and the return value needed for the next step. It falls short of mentioning prerequisites such as login and does not address the notes field, though notes are optional and not essential for 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 coverage is 80%, so the baseline is 3; the description adds a concrete outreach example for why and enumerates source_ai values, but it mostly repeats schema information and omits the notes parameter. The 'Also set source_ai' wording is slightly ambiguous because source_ai is optional in 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 opens with 'Create a lead group (campaign)', a specific verb and resource, and clarifies the required inputs and the downstream crm_add_leads step. This clearly differentiates it from CRM list/get/update siblings.

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?

It prescribes required fields (name + why), recommends source_ai, and links the returned group id to crm_add_leads, giving an agent a clear creation workflow. It does not explicitly name alternatives or exclusions, but the intended use is evident from the CRM sibling list.

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