attach_course_browser

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

With no annotations, the description carries the full burden, and it does disclose one meaningful negative behavior: no browser is launched, and a live tab plus controller-supplied DOM are required. It says nothing about prerequisites (must start_course_browser run first?), failure modes if the tab_id is stale, or whether binding steals focus or invalidates the prior session.

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?

Two terse sentences, front-loaded with the action and followed by the key constraint; there is no filler. It is arguably too short given the parameter load, but that gap is scored under completeness rather than here.

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?

A four-required-parameter binding tool with no annotations cannot be adequately specified in two sentences. The output schema covers return values, but prerequisites, what 'bind' changes about the page/browser state, and the meaning of the inputs are all missing.

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. "Controller supplies DOM" hints that html_source is the page markup handed in by the caller, but tab_id, browser_id, and page_url have no stated meaning, format, or source.

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?

States a specific verb and resource: bind (attach to) an existing Edge tab. The second sentence adds scope — the controller supplies DOM and MCP launches nothing. It does not, however, distinguish itself from near-siblings like attach_exam_browser or start_course_browser, leaving the agent to infer which attach variant applies.

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?

"Bind the existing Edge tab" implies the precondition that a tab already exists, and "MCP opens no browser" implicitly contrasts with start_course_browser. But no alternative is named and no explicit when-not condition is given, so the routing is inferred rather than stated.

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