Create Assignment

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

The description says 'Create a new assignment,' implying an additive, non-destructive operation, but annotations mark destructiveHint: true. This is a direct contradiction: creating a new assignment should not be flagged as destructive. The description also adds no behavioral context beyond the raw action.

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 efficient sentence with no wasted words and the core purpose is front-loaded. It is concise, though it sacrifices useful context that could have been included without bloating the 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?

Although the schema is complete and no output schema is required, the description lacks necessary context about behavior, return values, and the conflicting destructive annotation. For a mutation/create tool, the description should at least clarify whether it overwrites, publishes, or interacts with existing course data; it does none of this.

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 100%, so the schema fully documents all 7 parameters, including required fields course_id and name. The description adds no parameter-level meaning beyond the schema, which is the expected baseline at this coverage level.

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 and resource: 'Create a new assignment in a course.' It clearly distinguishes this tool from siblings like create_new_quiz, create_course, and update_assignment by naming the assignment resource and the course context.

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 no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The intended use is only implied by the word 'create' and the resource name, with no comparison to related assignment tools like update_assignment or create_new_quiz.

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