observe_course_browser

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

No annotations are provided, so the description carries the full disclosure burden. It does add one genuinely useful behavioral fact — no network access, so it is a pure local DOM parse — and implies a bound-tab prerequisite, but it never states that it is read-only/side-effect free, what it returns, or what happens on parse failure.

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 front-loaded sentence with no filler; the key noun phrase ('course directory or chapter-quiz DOM') arrives immediately. It is terse to the point of under-specification given the schema gaps, but nothing in it is wasted.

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 explained, but with four undocumented required parameters, zero schema coverage, and no annotations, a one-line description leaves too much for the agent to infer before a correct call.

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?

Schema description coverage is 0% across four required parameters, so the description must compensate and largely does not. 'The bound tab' loosely gestures at tab_id/browser_id and 'DOM' gestures at html_source, but page_url and the relationship between tab identifiers are entirely unexplained.

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 ('Parse') plus specific resource ('course directory or chapter-quiz DOM') and a scope note ('from the bound tab, without network'). An agent knows what it does, but nothing distinguishes it from close siblings such as observe_chapter_quiz or inspect_owned_page, which the description never references.

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 to call this versus the many adjacent observation tools (observe_chapter_quiz, inspect_owned_page, find_chapter_links). 'Without network' is a constraint, not usage guidance, and no prerequisites (e.g. an attached/bound browser) are stated as conditions for calling.

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