create-assignment-group

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

Annotations only provide destructiveHint=false, and the description does not disclose any additional behavioral traits such as permissions, defaults, side effects, or return values. It merely restates the create action and the required courseId, adding no behavioral context beyond what the name and schema already convey.

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 a single, succinct sentence that is front-loaded with the core purpose. Every word adds value, and the exception note 'All fields optional except courseId' is useful, making it highly concise without wasted text.

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 the tool creates an assignment group with seven parameters, no output schema, and sparse annotations, the description is too minimal. It does not explain what an assignment group is, what the various fields do, or what the caller should expect in response. This is a significant gap for a create operation.

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 only 14% (only courseId is described). The description does not explain any of the six undocumented parameters (name, rules, position, group_weight, sis_source_id, integration_data). The statement 'All fields optional except courseId' merely echoes the schema's required field and does not compensate for the lack of parameter meaning.

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 uses a specific verb ('Create') and resource ('assignment group (bucket) in a course'), which clearly distinguishes it from sibling tools like create-assignment or list-assignment-groups. The parenthetical 'bucket' adds immediate conceptual clarity.

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 does not explicitly state when to use this tool versus alternatives, but the name and 'create a new assignment group' strongly imply its use case. The only usage guidance is 'All fields optional except courseId,' which is a parameter constraint rather than a contextual usage guideline.

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