List Quiz Questions

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

The annotations already declare readOnlyHint=true, so the description is not responsible for establishing safety. It adds the 'all questions' scope but does not disclose pagination, ordering, or whether full question details and answer choices are returned. This is adequate but not enriching.

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?

A single, front-loaded sentence with no filler or redundancy. For a simple list operation, this is an appropriately concise definition.

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 low-complexity, read-only list tool with two documented required parameters, the definition covers the essential calling contract. It loses a point because there is no output schema and no note about what fields each question returns, and because the classic-vs-new-quiz distinction is left implicit.

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% and both parameters have clear descriptions ('The Canvas quiz ID', 'The Canvas course ID'). The tool description adds no additional parameter-level meaning, so it sits at the baseline for a well-documented 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?

The description uses a specific verb ('List') and a concrete resource ('all questions in a quiz'), making the core operation clear and separating it from tools like list_quizzes and get_quiz. It falls short of a 5 because it does not explicitly distinguish classic quiz questions from New Quiz items, despite siblings like list_new_quiz_items existing.

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?

No guidance is provided about when to use this tool versus alternatives such as get_quiz, list_quiz_submissions, or list_new_quiz_items. There are no conditions, prerequisites, or exclusions, so the agent must infer usage entirely from the name and terse description.

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