List New Quizzes

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

Annotations already establish read-only and idempotent behavior. The description adds value by explaining the mechanism (via assignment shells) and the instructor-gated limitation for question reading, giving context beyond the annotation flags without contradicting them.

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, front-loaded with the main purpose, then the exclusions and a caveat. Every sentence adds information and there is no padding 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?

For a simple list tool with one required parameter, the description conveys what it returns (a list of New Quizzes), how it works (via assignment shells), and what it doesn't cover (due dates/points/status). It's complete enough for an agent to call correctly, though an output schema would further clarify the return shape.

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 fully documents the single parameter courseId with type and pattern, and schema coverage is 100%. The description adds no additional parameter-specific information, so the baseline of 3 is appropriate; the description doesn't enhance parameter understanding beyond the schema.

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?

States clearly what it does: lists a course's New Quizzes (Quizzes.Next engine), and explicitly distinguishes it from the sibling canvas_list_quizzes by noting those quizzes don't appear there. The verb 'List' and resource 'New Quizzes' are specific and 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?

Provides explicit when-to-use guidance by referencing the alternative (canvas_list_quizzes) and explaining that this tool finds New Quizzes via assignment shells. It also cautions about the instructor-gated API for reading questions, helping agents set expectations about what fields are not available.

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