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

The description discloses that results are ordered by sort_order and that each question includes options and the correct answer. Since no annotations are provided, this adds valuable behavioral context beyond the basic 'list' operation, though it doesn't mention pagination or error conditions.

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 two concise sentences, front-loaded with the action, and contains no unnecessary information. Every clause adds value: the listing action, the quiz scope, the ordering, and the payload content.

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 list operation with one parameter and no output schema, the description covers the essential return details: questions are ordered and include options and correct answer. It is sufficient for an agent to understand what the tool will return and how it behaves.

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 has a single quiz_id parameter with 0% description coverage in the schema. The description refers to 'for a quiz' which gives some context, but it doesn't explicitly name the parameter or explain its required format. The schema pattern provides format details. The description adds minimal compensating value.

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 identifies the tool as listing all questions for a quiz, with a specific verb and resource. It also distinguishes itself from sibling tools like list_quizzes (which lists quizzes) and get_quiz (which retrieves a quiz), as well as create/update quiz question tools.

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 usage is implied: when you need all questions for a specific quiz. However, there is no explicit guidance on when to use this over alternatives like get_quiz or list_quizzes, and no exclusions or prerequisites are mentioned.

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