create_user

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the creation behavior, defaults for role and campaign_access, and the campaign_id dependency, but it omits potential side effects such as invitation emails, duplicate user checks, or required permissions.

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 well-structured with an action statement, Args section, Returns, and Examples. It is compact and free of redundant content, with each element serving a clear purpose for invocation.

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 6 parameters, 3 required, and no annotations, the description covers all parameters, defaults, return type, and usage examples. It is complete enough for an agent to select and invoke the tool correctly, especially given the presence of an 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?

The input schema has 0% description coverage, but the description fully compensates by explaining every parameter: email, first_name, last_name, role (with default), campaign_access (allowed values and default), and campaign_id (tied to restricted access). The examples illustrate typical parameter combinations, adding valuable meaning 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 opens with 'Create a new user in AgencyAnalytics,' clearly specifying the action and resource. It distinguishes itself from sibling tools like update_user, list_users, and delete_user by using the 'create' verb with the 'user' resource.

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 adding a new user through its examples and parameter details, but it does not explicitly state when to use this tool over alternatives. There are no exclusions or clear 'use this when' guidance, leaving the context partially implicit.

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