edubase_get_quiz

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds minimal behavioral context beyond 'Get/check' and the content hint. It does not disclose error behavior, permissions, or any side effects, but since annotations cover the safety profile, a score of 3 is appropriate.

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 short with two sentences, no wasted words. The first sentence states the action, the second adds context. The second sentence is a fragment but still clear. It is front-loaded and efficient.

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 presence of an output schema, the description does not need to detail return values. However, for a simple tool with one param, the description could better clarify what the 'quiz set' contains and how it differs from related tools. It is minimally sufficient.

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' is described in the schema as 'Quiz identification string' (100% coverage). The description does not add additional semantics like format, examples, or origin of the ID. Baseline 3 is correct for high schema coverage with no extra value.

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 'Get/check' as a verb-resource pair and mentions that the quiz set contains questions and powers exams. However, it does not clearly differentiate from sibling tools like edubase_get_quiz_questions or edubase_get_exam, which deal with related concepts.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it. Sibling tools exist for quiz questions and exam results, but the description provides no help in choosing.

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