canvas_create_assignment_group

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

With no annotations, the description carries the full behavioral burden. It correctly and prominently flags 'MUTATES the course', which is valuable, but does not disclose required permissions, whether duplicate groups are allowed, error behavior, or side effects beyond creation. The mutation flag is useful but incomplete.

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 purpose is front-loaded in the first sentence and the mutation warning is immediate. The Args block is structured and necessary given the schema's lack of descriptions, though slightly list-like rather than fully integrated. No sentences are wasted.

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 4-parameter mutation tool with no annotations and an output schema, the description covers parameter semantics and mutation status well, and the output schema handles return values. However, it omits usage context relative to siblings and behavioral details like permissions, leaving some gaps.

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 0%, so the description must compensate. It explains all four parameters: name with an example, group_weight as a percentage for weighted courses, position as a 1-based slot, and course_id as a numeric ID defaulting to CANVAS_DEFAULT_COURSE_ID. This fully covers the semantic gap in 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?

States a specific verb and resource ('Create an assignment group') and clarifies the domain with '(a gradebook category)'. This is clear and distinct from sibling tools like canvas_create_assignment, though it does not explicitly name or differentiate itself from those alternatives.

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 gives parameter-level usage ('Omit for unweighted', 'omit to append') but provides no guidance on when to choose this tool over alternatives such as canvas_list_assignment_groups or canvas_create_assignment. No prerequisites or exclusions are mentioned.

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