create_assignment

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

With no annotations, the description must carry the behavioral burden. It only states that an assignment is created, and does not disclose effects like whether the assignment is initially unpublished, whether there are permission requirements, idempotency, or what happens on duplicate names. It is not misleading, but it is nearly silent.

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?

One front-loaded sentence states the core action and resource with no waste. Every word earns its place; this is as concise as a purpose statement can be.

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 mutation tool with 7 parameters, 2 required, no annotations, and no output schema, a single purpose sentence is insufficient. It does not explain return behavior, creation side effects, or the meaning of optional fields beyond what the schema already states.

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 structured property descriptions already document every parameter. The description adds no parameter-level meaning beyond echoing course scope, so the 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 uses a specific verb ('Create') and resource ('new assignment') with the Canvas course scope, so an agent can tell it from list, get, and update assignment tools. However, it does not explicitly differentiate it from sibling create_* tools like create_announcement or create_discussion, so it falls just short of a 5.

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?

There is no guidance on when to choose this tool over alternatives such as update_assignment or list_assignments. The verb 'Create' implies one use case, but no prerequisites, exclusions, or alternative routing are provided.

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