create_quiz

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 discloses that the quiz is created as 'unpublished' and clarifies parameter formats, but it does not mention return values, permissions, or side effects. This is adequate for a simple creation but leaves gaps.

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, front-loaded sentence that immediately states the core action and state, followed by two essential parameter clarifications. No filler or repetition.

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 7 parameters, no annotations, and no output schema, the description is too sparse. It omits return value (e.g., quiz ID), prerequisites (e.g., course must exist), and how it fits into the quiz-creation workflow. A simple create tool still needs more behavioral context.

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?

With 0% schema description coverage, the description must compensate for all 7 parameters. It clarifies due_at (ISO-8601 UTC) and time_limit (minutes), which are non-obvious, but the other five parameters (title, course, description, allowed_attempts, assignment_group_id) are left to inference from their names. Partial compensation.

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 verb ('Create') and resource ('an empty quiz, unpublished'), which distinguishes it from sibling tools like add_quiz_questions and finalize_quiz. The qualifiers 'empty' and 'unpublished' define the exact state of the created object, making the purpose unambiguous.

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 implies when to use the tool (create an empty quiz before adding questions/finalizing) but does not explicitly state alternatives or when not to use it. Context from sibling tools (e.g., add_quiz_questions, finalize_quiz) suggests a workflow, but the description itself lacks direct guidance.

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