edubase_get_quizes

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context about the hierarchical level of quiz sets, but does not disclose additional behavioral traits (e.g., pagination behavior, auth needs, or rate limits). Given the annotations, the description provides adequate supplementary context.

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: the first identifies the action and scope, the second defines the resource. There is no extraneous information, and it is efficiently front-loaded with the core purpose.

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?

Considering the presence of an output schema and the tool's simplicity (a listing operation), the description is mostly complete. It explains what quiz sets are and what the tool retrieves. A minor gap is the absence of guidance on when to use this vs. other listing tools, but given the output schema covers return structure, it is not severely incomplete.

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%, so the input schema fully documents all three parameters (search, limit, page). The description does not add any further meaning or example usage for these parameters, thus meeting the baseline expectation for high 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 tool lists 'owned and managed Quiz sets' and defines a quiz set as 'named collections of questions that sit at the middle level of the EduBase Quiz hierarchy.' This verb+resource+scope is specific and distinguishes it from siblings like edubase_get_quiz (which likely retrieves a single quiz) and edubase_get_quiz_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 guidance on when to use this tool versus alternatives such as edubase_get_quiz or other listing tools. There is no mention of prerequisites, preferred input conditions, or when not to use it.

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