Locate and open a chapter quiz by clicking the quiz tab and lazy-scrolling until the quiz iframe appears. Use it to reach chapter assessments in StudyFlow workflows.
Locate the chapter-quiz iframe: click the quiz tab and lazy-scroll until found.
| Name | Required | Description | Default |
|---|---|---|---|
| polls | No | ||
| click_tab | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.9.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool clicks a tab and repeatedly scrolls until the iframe is found, but it omits failure behavior, timeout/attempt limits, and any side effects of the click/scroll sequence.
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 definition is a single front-loaded sentence with no filler. The colon structure efficiently moves from the goal to the procedure.
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 browser-automation step with no annotations, the description is incomplete: it omits preconditions (e.g., being on a chapter page), parameter meanings, and what happens if the iframe is not found. The output schema can cover return values, but the call context remains underspecified.
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?
With 0% schema description coverage, the description must explain the two parameters. It hints at 'click the quiz tab' (click_tab) and 'lazy-scroll until found' (possibly polls), but never defines what 'polls' controls or how click_tab changes behavior.
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 verb ('Locate') and resource ('chapter-quiz iframe'), so the core action is clear. However, it does not differentiate this tool from siblings like observe_chapter_quiz or submit_chapter_quiz, leaving the agent to infer the exact role.
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 sentence describes a procedure ('click the quiz tab and lazy-scroll until found') but gives no when-to-use condition, prerequisites, or alternative tool. An agent must infer that this is the step for opening a quiz before observing or submitting.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.