create_assignment

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

No annotations are provided, so the description carries the full burden. It clarifies the scope (regular assignments only) but does not disclose behavioral traits such as default publication state, permission requirements, or side effects. It is not misleading, but lacks depth beyond the purpose statement.

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 two sentences, front-loaded with the main purpose and followed by concise exclusions. Every word earns its place, with no redundancy or filler.

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 11 parameters, full schema coverage, and no output schema, the description provides sufficient context for a basic create operation. It explains the tool's scope and exclusions effectively, though it omits any mention of prerequisites or error behavior. This is acceptable, as the schema covers parameters.

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 baseline is 3. The description does not add meaning to individual parameters; it only points to alternative tools for other assignment types. The schema fully documents parameter meanings, so no deduction is needed.

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 a new regular assignment in a course, using a specific verb and resource. It explicitly distinguishes itself from sibling tools by directing graded discussions to create_discussion and New Quizzes to create_new_quiz.

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 explicit when-to-use guidance ('Create a new regular assignment in a course') and when-not-to-use guidance with named alternatives for graded discussions and New Quizzes. This leaves no ambiguity about tool selection.

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