edubase_get_quiz_questions

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds the hierarchy context but does not reveal additional behavioral traits such as pagination, permissions, or output format. With annotations handling the core safety traits, the description is adequate but not above baseline.

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 sentences, front-loading the main action and adding only necessary context about hierarchy. No redundant or vague wording, making it highly concise.

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?

Given the simple tool with one required parameter and existing output schema, the description provides enough context about the resource structure. It could optionally mention pagination or ordering, but this is not essential for a basic list operation. The hierarchy explanation adds value beyond minimal completeness.

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 single parameter 'quiz' has a schema description ('Quiz identification string') covering 100% of parameters. The tool description does not add further meaning or constraints beyond the schema, so it remains at baseline 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 declares the tool lists all questions and question groups in a quiz set, clarifying the hierarchy between questions, quiz sets, and exams. This clearly specifies the verb (list), resource (questions and question groups), and scope (in a quiz set), distinguishing it from sibling tools like edubase_get_question or edubase_get_questions.

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 provides no explicit guidance on when to use this tool versus alternatives like edubase_get_question or edubase_get_questions. While the hierarchical context is helpful, there are no direct statements about when to choose this tool or exclude others.

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