list_new_quizzes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context by revealing the implementation approach ('by filtering assignments') and the nature of the return value ('Returns a summary of each'). This goes beyond a minimal description, though it could further disclose potential performance implications or output field specifics.

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 concise sentences, front-loaded with the main purpose and output, followed by important alternative references. Every sentence earns its place with no redundancy.

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?

This is a simple one-parameter list tool with no output schema or annotations. The description explains what the tool does, how it works, what it returns, and how to use related tools, making it fully sufficient for selecting and invoking it correctly.

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 coverage is 100% (the single parameter course_id is described as 'Canvas course ID'), so the schema already fully documents the parameter. The description adds no additional parameter-specific meaning, warranting the baseline score of 3.

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 ('List') and clearly identifies the resource ('New Quizzes (Quizzes.Next) in a course'). It also distinguishes itself from sibling tools by pointing to get_new_quiz for full details and quiz item tools for question management.

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 explicitly states when to use this tool (to list all New Quizzes) and provides direct alternatives for related needs (full details via get_new_quiz, question management via list_quiz_items/create_quiz_item). This is clear guidance on selection.

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