List Quiz Questions

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

The readOnlyHint and openWorldHint annotations already convey the read-only nature of the tool, and the description does not contradict them. However, the description adds no additional behavioral context, such as pagination, ordering, or error behavior, beyond what the annotations already provide.

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, direct sentence contains all the necessary information without any fluff. It is appropriately minimal for the simplicity of the operation.

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 lack of an output schema and the potential ambiguity with list_new_quiz_items, a note about scope (e.g., classic vs. new quizzes) or pagination would improve completeness. The description is functional but omits contextual details that would help an agent avoid common mistakes.

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 documents both parameters (course_id, quiz_id) with short descriptions, achieving 100% schema coverage. The tool description adds no additional parameter-level detail, but per the rubric the baseline of 3 is appropriate when the schema already covers parameters fully.

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 ('List') and resource ('all questions in a quiz'), clearly stating the operation. However, it does not clarify whether this applies to classic vs. new quizzes, while sibling tools like list_new_quiz_items suggest such a distinction exists.

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?

Usage is implied by the name and parameter schema, but the description gives no explicit guidance on when to prefer this tool over alternatives like list_new_quiz_items or list_quizzes. No exclusions or contexts are mentioned.

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