edubase_get_exam_skills

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which cover the behavioral profile well. The description adds no extra behavioral context beyond what annotations already provide, but it does not contradict them either.

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, clear sentence that immediately conveys the tool's purpose. It is concise, front-loaded, and contains no unnecessary words or repetition.

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 tool's simplicity (one parameter, with an output schema and rich annotations), the description is sufficient. It covers the core function. However, it could be slightly more complete by explicitly noting that the output schema defines the return structure, but this is already implied by the presence of an output schema.

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 a description for the 'exam' parameter ('exam identification string'). The description provides context ('Quiz set used by an exam') that ties the parameter to the tool's purpose, but it does not add significant new meaning beyond the schema's existing description.

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 it retrieves skills defined in the quiz set associated with an exam. It identifies the specific resource and context. However, it does not explicitly differentiate from the similar sibling tool edubase_get_quiz_skills, which retrieves skills from a quiz directly, potentially causing confusion about when to use which.

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 when wanting skills from an exam's quiz set but provides no explicit guidance on when to use this tool versus alternatives like edubase_get_quiz_skills or when not to use it. There is no mention of prerequisites or conditions.

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