get-quiz-question

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

The readOnlyHint annotation already declares that this is a read-only operation, and the description does not contradict it. However, the description adds no additional behavioral context—it does not mention return format, potential errors, or any side effects. With the annotation covering the safety aspect, the description provides no extra transparency.

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, concise sentence of seven words. It is front-loaded with the verb and resource, contains no unnecessary information, and earns its place.

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?

The tool has no output schema, so the agent cannot infer the return value from structured data. The description also does not state that it returns a full question object or describe any edge-case behavior. For a fetch operation, this is a notable gap, even though the tool is simple and the annotations provide some safety context.

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 covers all three parameters (courseId, quizId, questionId) with clear descriptions, achieving 100% coverage. The description adds no parameter-level meaning beyond what is already in the schema, so the baseline of 3 is appropriate.

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 identifies the resource as 'a single question from a quiz.' This clearly distinguishes it from sibling tools like list-quiz-questions (which fetches multiple questions) and get-quiz (which fetches the quiz itself). The purpose is unambiguous and actionable.

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 description implies usage when a specific question by ID is needed, but it does not explicitly mention alternatives or when to avoid this tool. The singular 'a single question' and the questionId parameter suggest a targeted lookup, but no exclusions or comparisons to siblings like list-quiz-questions are provided.

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