list-quizzes

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

The annotation `readOnlyHint: true` already declares this as a safe read operation. The description adds no further behavioral context such as pagination, ordering, or error behavior. It simply restates the purpose without disclosing any additional traits beyond the annotation.

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, concise sentence with no filler or redundant details. It efficiently conveys the tool's purpose and scope.

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?

Given the low complexity (one required parameter, no output schema, read-only annotation), the description is sufficient for an agent to understand the tool's basic function. However, it lacks details about return format (e.g., fields included) or pagination, but these are not critical for a simple list operation.

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?

The schema provides a complete description of the single parameter (`courseId`), so the baseline is 3. The description does not add extra meaning beyond what the schema already states, such as format or constraints.

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 tool lists all quizzes in a course, using a specific verb (`Get a list`), resource (`quizzes`), and scope (`in a course`). This distinguishes it from related tools like `get-quiz` (single quiz) and `create-quiz`.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives (e.g., `get-quiz` for a single quiz) or any prerequisites. The phrase 'in a course' implies a course context, but there is no explicit when/when-not guidance.

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