bulk_import_users

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

The description discloses key behaviors: up to 2000 users, upsert semantics based on username, and that unspecified fields are left unchanged. It also covers bulk enrollment. However, it lacks details on potential side effects (e.g., email sending when sendMessage is true), error handling, or rate limits. Since annotations are absent, the description could be more 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?

The description is concise with four sentences, each adding essential information. It front-loads the main purpose, then explains key behaviors without redundancy.

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?

The description covers core functionality well but does not explain the return value or error responses (no output schema). It also does not reference sibling tools or provide context on when to use this vs. other bulk operations.

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 schema has 100% description coverage, so baseline is 3. The description adds value by explaining the use of course fields with CourseCodeForBulkImport and reiterating the uniqueness of username, which goes beyond the schema descriptions.

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 or updates up to ~2000 users and/or bulk-enrolls existing users into courses. It distinguishes from sibling tools like assign_course_to_user or bulk_assign_course_to_users by focusing on user creation/update with optional course enrollment.

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 provides guidance on using course1–course3 fields with CourseCodeForBulkImport, explains that username is the unique key, and specifies that existing users are updated while new ones are created. However, it does not explicitly state when to use this tool versus alternatives like search_users or get_user.

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