sf_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 disclosure burden. It mentions that username must be globally unique, but does not discuss side effects, idempotency, authentication requirements, or error behavior. For a creation tool, more transparency about expected outcomes and constraints would be beneficial.

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 fairly concise, using a single paragraph with line breaks for readability. However, embedding the SOQL example directly makes it slightly less structured. Every sentence adds value, but a more structured format could improve clarity.

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 15 parameters (5 required) and no output schema, the description provides the absolute essentials but lacks explanations for many parameters, return values, or error handling. It is adequate for basic use but incomplete for complex scenarios.

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 low (27%). The description adds value by listing required fields and clarifying username format, but does not cover many optional parameters. It partially compensates by providing an external reference for profile_id, but overall, many parameters remain undescribed.

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 creates a Salesforce user, listing required fields and providing a practical example for obtaining ProfileId. It distinguishes this tool from sibling tools like sf_create (which likely handles generic objects) and sf_update, making its specific purpose unambiguous.

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 explicitly lists required fields and instructs users to get ProfileId via sf_read before using this tool, providing a concrete SOQL query example. It implies a prerequisite but does not explicitly state when to avoid using this tool or compare with alternatives.

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