list-quiz-questions

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

Annotations already declare readOnlyHint=true, covering safety. The description adds the 'all questions' scope, implying no filtering or pagination, but doesn't discuss ordering, response format, or rate limits. With annotations, 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?

The description is one short sentence ('Get a list of all questions in a quiz') with no filler or redundant information. Every word contributes to understanding the tool's purpose.

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 tool with clear parameters and readOnlyHint, the description is minimally sufficient. However, with no output schema, it doesn't specify the structure of the returned questions, which could be a gap for the agent.

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 100% for both required parameters (courseId and quizId). The description adds no additional parameter meanings or syntax, so it meets the baseline for adequate parameter documentation.

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 ('Get a list') and identifies the resource ('all questions in a quiz'). It clearly distinguishes from siblings like 'get-quiz-question' (single question) and 'list-quiz-question-groups' (question groups, not questions).

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 context is clear: use this tool when you need all questions for a quiz. While it doesn't explicitly state alternatives or when-not-to-use, the sibling tools' names imply other use cases (e.g., 'get-quiz-question' for a single question).

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