edubase_get_exam_skills

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds context about the data source (Quiz set used by an exam), which is useful but does not disclose return format, pagination, or failure behavior. It provides some value beyond annotations but not a rich behavioral overview.

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 states the essential function without any filler. It is front-loaded with the action and resource, and no words are wasted.

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-only retrieval tool with one well-documented parameter, an output schema present, and annotations indicating safe behavior, the description is adequately complete. An agent has all necessary cues to select and call the tool correctly.

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 schema description for 'exam' is 100% covered ('exam identification string'), so the baseline is 3. The description adds no additional parameter details or format hints beyond what the schema already provides.

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 a specific verb ('Get') and resource ('skills defined in the Quiz set used by an exam'), distinguishing it from related tools like edubase_get_quiz_skills or edubase_get_exam_settings. It explains the indirect relationship between exam and quiz set, leaving no ambiguity about what the tool returns.

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. It does not mention any sibling tools, edge cases, or prerequisites. The intent is implied from the name and description, but there is no explicit direction for an agent to choose this over edubase_get_quiz_skills or other getter tools.

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