canvas_list_quizzes

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

No annotations are present, so the description carries the full burden; it discloses an important domain quirk (New Quizzes surface as assignments with submission_type=external_tool), which is genuine behavioral context. It stops short of covering read-only nature, pagination, or result limits, so it is strong but not complete for an unannotated tool.

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 purpose is front-loaded in one line, the routing caveat follows immediately, and the Args block is terse. Every sentence carries information an agent needs; there is no 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?

An output schema exists, so return values need not be described, and the one parameter is covered. The remaining risk for this tool is the Classic-vs-New-Quizzes confusion, which the description addresses head-on.

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 description coverage is 0%, so the description must compensate, and it does: it specifies the parameter is numeric and that it defaults to CANVAS_DEFAULT_COURSE_ID when omitted, matching the empty-string default in the schema. This fully documents the single parameter, though it adds no format/validation detail beyond that.

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 a specific verb+resource ('List quizzes in a course') and goes further to scope which quiz system it covers (Classic Quizzes) and what it excludes. An agent can distinguish it from canvas_list_assignments and canvas_list_discussions without opening any schema.

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?

Explicitly states when to use this tool and what to do when it returns nothing ('check canvas_list_assignments if a quiz you expect is missing'), naming the concrete alternative. This is a real when/when-not/alternative rule, not implied guidance.

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