enter_selected_exam

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

With no annotations, the description carries the full burden, and it only says 'click' — it doesn't say a navigation occurs, what happens if zero or multiple exams are visible, or whether the action is reversible. The word 'uniquely' hints at a precondition (exactly one matching exam) but never states the failure behavior.

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?

A single short sentence with no padding, which is structurally fine, but the terseness comes at the cost of clarity ('uniquely visible named exam') rather than through efficient precision.

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?

An output schema exists so return values needn't be explained, but for a stateful browser-click tool in a large exam workflow the description omits required page state, the meaning of the sole argument, and post-click behavior. It is not enough for an agent to call this confidently without inspecting the schema or code.

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?

There is one required parameter with 0% schema description coverage, so the description must explain course_name — but it never mentions it. Worse, it says 'named exam' where the parameter is a course name, muddying rather than clarifying the mapping.

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 verb ('Click') and rough target (a named exam in the owned exam list) are stated, but the phrasing 'uniquely visible named exam' is jargon that leaves unclear whether the name refers to the exam or the required course_name argument. It also doesn't differentiate itself from nearby siblings such as open_course_exam or inspect_exam_page.

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 indication of when this tool should be chosen over open_course_exam, inspect_exam_page, or the browser/exam-loop families. There are no stated prerequisites (e.g., that the owned exam list must already be displayed) and no exclusion conditions.

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