edubase_get_exam_status

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's job is lighter. It adds useful context by stating that the returned status specifically conveys whether new tests can be started, which helps agents interpret the result. No contradiction with annotations.

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 clearly introduces the tool and its purpose. Every word contributes meaning; no filler or redundant phrasing.

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 tool with one required parameter, a full set of annotations, and an output schema, the description is complete enough. It might have added a note that the exam must already exist or how status values map to test-starting permission, but these details are likely captured in the output schema or the openWorldHint.

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 covers 100% of parameters with a description, so the baseline is 3. The description itself does not elaborate on the required 'exam' parameter, but the schema describes it as an exam identification string, which is sufficient for a single straightforward parameter.

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 states a specific operation: getting the status of an exam, and clarifies the semantics by noting the status indicates whether new tests can be started. This distinguishes it from sibling tools like the one that sets exam status (edubase_post_exam_status) and from generic exam retrieval tools.

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?

No guidance is provided about when to choose this tool over alternatives. The description and readOnly hint imply a read operation, but there is no explicit mention of the alternative setter tool (edubase_post_exam_status) or any condition that would favor a different getter.

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