로그인된 브라우저로 LMS 원문 열기

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

The description discloses key behaviors beyond the annotations: it opens a dedicated browser, does not automate, avoids putting cookies/tokens in URLs or command lines, and requires the user to authenticate on the official login screen. It also notes restrictions on allowed URLs/parameters.

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 description is compact and front-loaded with the main purpose, followed by usage trigger and security constraints. Each sentence adds relevant information with minimal redundancy.

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 simple navigation tool, the description covers what it does, when to use it, and important security behavior. It does not describe return values or failure modes, but no output schema is present and those details are less critical for this action.

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?

The URL parameter is explained as the LMS original URL returned by list/detail tools, which adds useful context beyond the URI format. It could be slightly more explicit about requiring a full valid URL, but the current description is sufficient.

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 clearly states the tool's purpose: opening the original LMS page in a dedicated Chrome/Edge browser without automation. It distinguishes this from sibling tools by emphasizing the external browser and non-automated nature.

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?

It explicitly gives a trigger condition: use when a chat link opens in an internal browser that is not logged in. It does not explicitly name an alternative sibling tool, but the condition is specific enough to guide selection.

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