inspect_course_score_page

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

With no annotations, the description carries the full burden; it does disclose non-navigation and non-submission, which is the most important safety trait here. It says nothing about whether a live browser session must already be attached, what 'observed links' means operationally (harvested hrefs? filtered?), or what happens on a page it cannot read.

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?

One front-loaded sentence with the safety constraint attached immediately; nothing is redundant. 'Observed links' is the one phrase that costs clarity without earning its place.

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 need not be described, but with 0% parameter coverage and a mutation-adjacent browser tool that has no annotations, the description should at minimum explain the page_url default and the session prerequisite. As written it is too thin for a 3-parameter browser-inspection 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?

Zero of the three parameters have schema descriptions, and the description adds no meaning for account_id or course_url beyond echoing 'enrolled-course'. The optional page_url with an empty-string default is completely unexplained — an agent cannot tell whether omitting it means 'use course landing page' or 'inspect all pages'.

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?

Specific verb (read) plus resource (enrolled-course score pages), and it names a secondary artifact (observed links). It does not distinguish itself from close siblings like inspect_owned_page, inspect_course, or inspect_exam_page, so scope overlap remains for an agent to guess at.

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 clause 'never navigate or submit' sets a hard boundary and implies this is a passive inspection step, but it never says when to prefer this over inspect_owned_page / inspect_exam_page or what precondition (attached browser, logged-in account) must hold. Usage is implied rather than guided.

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