canvas_quizzes

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds a meaningful limitation about New Quizzes and external platforms, though it does not mention pagination or return shape beyond what the schema implies.

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 concise sentences, with the core purpose front-loaded and the platform limitation immediately following. There is no redundant restatement of annotations or schema fields.

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 tool with full schema coverage and strong annotations, the description is mostly complete. It could better state collection scope and sibling routing, but the key limitation is disclosed and little else is missing.

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 already documents course_id, raw, and page including the pagination token format. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 and resource: read accessible classic Canvas quiz metadata. It implies a collection-level quiz resource through the plural name, but does not explicitly contrast with canvas_quiz or say it lists quizzes in a course.

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?

Implies use for classic Canvas quiz metadata and warns that New Quizzes and external platforms may only expose assignment metadata. It does not name alternatives such as canvas_quiz for a single quiz or canvas_assignments for New Quizzes, so routing must be inferred.

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