get-quiz-question-group

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

The annotation readOnlyHint=true already discloses this as a safe read operation, and the description's 'Fetch' aligns with it. The description adds no additional behavioral context beyond scope (single item), which is acceptable for a simple get, though not-found or error behavior is not mentioned.

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 sentence that front-loads the action and resource with no filler. Every word contributes to understanding, making it appropriately concise and well-structured.

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 operation with complete schema descriptions and a readOnly annotation, the description provides sufficient context. No output schema exists, but the intent is clear and the tool's simplicity means no additional details are needed.

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?

All three parameters (courseId, quizId, groupId) already have complete descriptions in the schema, so the description does not need to add meaning. It adds nothing beyond the schema, meriting the baseline score for high schema coverage.

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 states the action ('Fetch') and the target ('a single question group from a quiz'), using a specific verb and resource scope that distinguishes it from sibling tools like list-quiz-question-groups and delete-quiz-question-group.

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 phrase 'Fetch a single' implies the tool is for retrieving one specific question group, contrasting with the sibling list endpoint, but it does not explicitly name alternatives or exclusions. This provides clear context without meeting the highest explicit-guidance bar.

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