edubase_get_exams

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

The description adds minimal behavioral context beyond what the annotations already provide. Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which fully convey the behavioral traits. The description only adds that exams are built from quiz sets, which is background context rather than behavioral disclosure.

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 very concise with a single sentence. It is front-loaded with the action and resource, though it could include a bit more structure (e.g., mentioning that it supports pagination or filtering) without becoming verbose.

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 description provides hierarchical context (exams are top-level and built from quiz sets), which is helpful. Given that an output schema exists and annotations are comprehensive, the description does not need to explain return values. However, it could mention pagination or filtering behavior more explicitly.

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 has 100% coverage with descriptions for all 4 parameters. The description does not add any additional meaning beyond the schema, so a baseline score 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 clearly states the action ('List') and the resource ('owned and managed exams'). It also provides hierarchical context by noting that exams are the highest level in the EduBase Quiz hierarchy, built from Quiz sets. This helps differentiate from sibling tools like edubase_get_exam (singular), which retrieves a single exam.

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 through the verb 'list' and the hierarchical note, but it does not explicitly state when to use this tool vs. alternatives like edubase_get_exam or edubase_get_exam_tags. No exclusions or alternative guidance are provided.

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