Authenticate with SMU eLearn

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

With no annotations, the description carries the full transparency burden. It discloses the sequence (open, wait, verify, save, close) and mentions 'owner-only session state,' which hints at file writes. However, it omits critical behavioral details: it does not state that interactive MFA may be required, that Chrome will close disrupting other tabs, or any failure/timeout behavior. This is a moderate gap.

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 a single sentence that front-loads the purpose and outlines the entire workflow with zero wasted words. It is concise, readable, and efficiently conveys the tool's core function.

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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is incomplete. It does not explain parameter usage, nor does it specify the return value or success/failure indicator, and it lacks explicit mention of user interaction needs (MFA). An agent would struggle to invoke it correctly without additional documentation.

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 coverage is 0%, so the description must compensate. It only indirectly references 'wait one minute by default' (matching initialWaitSeconds default), but never names or explains timeoutSeconds or pollIntervalSeconds. The agent cannot infer parameter meaning from the description, which is a clear deficiency.

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 ('Authenticate'), a clear resource ('SMU eLearn'), and describes the full process (open Chrome profile, wait, verify, save state, close). It is immediately distinct from all sibling tools, which focus on documents/courses, not authentication.

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 description provides no guidance on when to use this tool versus alternatives like elearn_auth_status, nor does it state preconditions (e.g., must be logged out, or must run before other tools). It implies usage only through its purpose, leaving the agent to infer when authentication is needed.

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