List Quizzes

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and 'List' is consistent with that read-only profile. The description adds only the course scope, with no extra behavioral detail such as return shape, pagination, or whether unpublished quizzes are included.

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 six-word sentence with no filler and the action is front-loaded. It is appropriately compact for a tool with one required parameter.

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 one-parameter read-only listing tool, the description is sufficient to invoke: the only required input is clearly documented in the schema. There is no output schema, but 'List all quizzes' adequately signals a returned list, and the low complexity lowers the completeness burden.

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%: course_id is required and described as 'The Canvas course ID'. The description mentions 'in a course' but adds no additional parameter syntax, constraints, or format details 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?

The description uses a specific verb and resource ('List all quizzes in a course') and clearly indicates scope. It does not explicitly contrast with siblings like get_quiz or list_new_quiz_items, so it doesn't fully differentiate classic quizzes from new quiz item tools.

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 on when to use this tool versus alternatives such as get_quiz or list_new_quiz_items. The description implies a bulk-listing use case but states no exclusions, prerequisites, or sibling routing.

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