bulk_assign_course_to_users

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

Without annotations, the description adds one behavioral trait (rate limit handling) but lacks detail on other behaviors like idempotency, error handling, or partial success. Adequate but not rich.

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?

Two sentences, no wasted words. Key information is front-loaded: first sentence states purpose, second gives usage directive and behavioral note.

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 simple tool with 2 required params and no output schema, the description covers purpose and usage sufficiently. Lacks details on return values or errors but is adequate for the complexity level.

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 covers both parameters (courseId, userIds) with descriptions. The tool description adds no additional semantic meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 'Assign a course to a list of users' with a specific verb and resource, and explicitly distinguishes itself from the sibling tool 'assign_course_to_user' by advising not to call it repeatedly.

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 guidance ('when registering or enrolling multiple users into a course') and what not to do ('do NOT call assign_course_to_user repeatedly'), plus a behavioral note about respecting rate limits.

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