list-quiz-question-groups

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

The annotation readOnlyHint already declares the tool's safe read-only nature. The description adds scope ('all question groups') but doesn't disclose return format, ordering, pagination, or other behavioral traits. This is acceptable but minimal.

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 clear sentence that is front-loaded and contains no unnecessary words or 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?

For a simple read-only list operation with a well-defined schema, the description adequately covers the essential function. It doesn't mention return format, but no output schema exists to shift the burden, and the operation's simplicity makes this sufficient.

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 input schema describes both parameters (courseId and quizId) with 100% coverage, so the description doesn't need to add parameter-specific meaning. It provides no extra detail, which matches the baseline.

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's purpose with a specific verb ('get a list'), resource ('question groups'), and scope ('in a quiz'). It effectively differentiates from siblings like get-quiz-question-group (singular) and create/update/delete operations.

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?

The description implies the tool is for listing all question groups for a given quiz, which is distinct from fetching a single group. It doesn't explicitly name alternatives, but the context is clear and no exclusions are needed for a simple read-only list.

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