edubase_post_exam_status

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

Beyond the annotations, the description discloses a non-obvious side effect: 'Disabling new tests also cancels the scheduled automatic disabling of the exam.' It also clarifies that the exam stays active, preventing a misunderstanding that disabling new tests closes the exam.

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 compact and front-loaded, with the core action stated first followed by necessary constraints and side effects. Every sentence adds useful information, and there is no redundant or filler text.

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?

With two well-documented parameters, an output schema, and no nested objects, the description provides sufficient context: valid conditions, behavior, and side effects. An agent has enough information to select and invoke this tool.

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 already documents both parameters fully, with 'exam' as an identification string and 'status' as a boolean allowing new tests. The description adds operational context but does not materially extend the parameter-level meaning beyond what the schema provides, so the baseline 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 uses a specific verb and resource: 'Enable or disable starting new tests on an exam.' It clearly differentiates this write operation from the read-only sibling edubase_get_exam_status by explaining that the exam itself remains active and only test-starting is controlled.

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?

It explicitly states when the operation is valid ('while the exam is active and has not closed yet') and when it is not ('New tests cannot be started in the results viewing period'). This gives the agent clear conditions for invoking the tool correctly.

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