get-quiz

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

The description is consistent with the readOnlyHint=true annotation and adds the nuance that it returns 'metadata' rather than full quiz details. However, it does not disclose additional behavioral aspects such as error handling, authorization, or what exactly 'metadata' includes.

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, compact phrase that conveys purpose without redundancy or unnecessary words. It is front-loaded and immediately understandable.

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 tool with two clearly described parameters, the description is mostly adequate. However, with no output schema, it leaves the contents of 'metadata' vague, and it doesn't explicitly contrast with list-quizzes for single-item use cases.

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 provides complete descriptions for both quizId and courseId (100% coverage), so the description does not need to repeat them. It also adds no extra semantic meaning to the parameters; the baseline of 3 applies.

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 the specific verb 'Fetch' and resource 'metadata for a single quiz', clearly identifying a single-item read operation. This distinguishes it from sibling tools such as list-quizzes (which fetches many) and get-quiz-question (which targets a different resource).

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 only implied by the phrase 'single quiz'; there is no explicit guidance on when to prefer this over list-quizzes or other quiz-related tools. No alternatives or exclusions are mentioned.

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