create_new_quiz

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

The description discloses that it returns the created quiz object including assignment_id, which is helpful. However, there are no annotations, so the description must carry the full burden of behavioral disclosure. It doesn't mention permissions, reversibility, or side effects beyond returning a quiz. The 'Create' action implies mutation, but specific traits are limited.

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?

Two sentences, direct and efficient. It immediately states the purpose and the key return information without unnecessary detail.

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 create tool with 6 parameters and no annotations, the description is fairly complete. It specifies the return value, identifies Quizzes.Next, and the schema covers parameters. However, it lacks explanation of prerequisites or default behaviors (like whether unpublished quizzes are created by default), which would be useful.

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?

The schema has 100% coverage for parameters, so the schema already provides all parameter descriptions. The tool's description adds no additional parameter semantics—it only mentions the return value. Thus, the baseline of 3 applies.

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?

Clearly states the action (Create), the resource (a New Quiz in Quizzes.Next), and context (in a course). This distinguishes it from create_assignment and create_quiz_item, and the mention of Quizzes.Next differentiates from any classic quiz tools.

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 a clear indication of what the tool does, but no explicit guidance on when to use it versus alternatives like create_assignment or update_new_quiz. It implies use when creating a new quiz in Quizzes.Next, but doesn't explicitly exclude other scenarios or mention alternatives.

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