get_new_quiz

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Get' implies a read-only operation, and the listed content adds context, but permission requirements, error behavior, and return format are not addressed.

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 with no redundancy. The purpose is front-loaded, and the second sentence provides actionable parameter guidance without unnecessary filler.

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?

With no output schema and no annotations, the description covers the tool's scope and key fields (settings, time limits, configuration) and gives parameter discovery guidance. It lacks return structure or error semantics, but for a straightforward getter with high schema coverage, it is sufficiently complete.

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%, providing a baseline of 3. The description adds valuable meaning for assignment_id by explaining it is a Canvas assignment ID discoverable via list_new_quizzes or list_assignments with is_quiz_lti_assignment=true, exceeding the minimal schema description.

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 'Get' and the resource 'full details of a single New Quiz', specifying Quizzes.Next and the included content (settings, time limits, configuration). This distinguishes it from sibling tools like get_assignment and get_quiz_item.

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 provides practical guidance for finding assignment_id via list_new_quizzes or list_assignments, but does not explicitly state when to prefer this tool over siblings such as get_assignment or get_quiz_item. Usage context is implied rather than explicit.

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