Login With Password

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

No annotations provided, so description carries full burden. It mentions login attempt, server-side storage, and session ID return, but does not disclose failure behavior, side effects, or prerequisites. Lacks details on persistence or security implications.

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?

Single, front-loaded sentence with no wasted words. Could be slightly expanded but remains efficient.

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?

Tool has 4 parameters and no output schema. Description lacks details on error handling, session management, password safety, or how the returned session_id should be used. Incomplete for a login 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?

Schema coverage is 0%, meaning no parameter descriptions in schema. Description does not explain any parameter beyond types. Critical parameters like 'login_path' and 'include_cookie_header' are left undefined, leaving the agent guessing.

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?

Description clearly states the action (login), the resource (Moodle form), and the outcome (stores cookies/sesskey, returns session_id). It distinguishes from sibling login tools by specifying Moodle form login.

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?

Description implies usage for password-based login but lacks explicit when-not-to-use guidance or alternative tools. Among siblings, there are other login methods (e.g., browser_login, bootstrap_session) that could be mentioned.

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