Get Quiz

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety floor is covered; the description goes beyond them by warning that quiz instructions are 'fenced as untrusted' (prompt-injection handling) and that the server never takes quizzes. It stops short of covering error behavior for missing or inaccessible quizzes.

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?

Four short sentences, zero filler, with the resource identification front-loaded and the security note placed after the payload contents. Every sentence carries information an agent can act on.

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?

With no output schema, listing the returned fields gives an agent a real expectation of the response shape, and the untrusted-content note covers the main behavioral risk. Missing only edge-case behavior (nonexistent quiz ID, New Quiz ID passed by mistake).

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%, with both course_id and quiz_id documented including where to obtain them, so the baseline of 3 applies. The description adds nothing about parameter meaning or formats beyond what the schema already states.

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?

States a specific verb and resource ('Get one Classic Quiz') and enumerates what the returned record contains (instructions, time limit, allowed attempts, dates, results visibility). Naming 'Classic Quiz' implicitly separates it from the New Quizzes siblings (get_new_quiz, list_new_quizzes) without needing the schema.

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?

Adds two real usage boundaries: it is read-only and 'this server never takes quizzes', which steers an agent away from attempting submission flows. It does not explicitly say to use get_new_quiz for New Quizzes records, but that routing is supplied by the quiz_id parameter description referencing list_quizzes vs list_new_quizzes.

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