login

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

Despite no annotations, the description fully discloses behavior: saves cookie to ~/.config/hrms-mcp/cookies, persists automatically, and returns success/failure with session validity. No contradictions.

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?

Description is efficient with no wasted words. It front-loads the main purpose, then provides step-by-step instructions, and ends with return behavior. Each sentence earns its place.

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 simplicity (single parameter, no nested objects) and presence of an output schema (which details return values), the description is complete. It explains the return format (success/failure and validity) adequately.

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 single parameter is fully described in the schema with 100% coverage. The description adds value beyond the schema by providing context on how to obtain the cookie (DevTools instructions) and an example value format, elevating it above baseline 3.

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 it saves the HRMS session cookie to enable all other tools, using the verb 'save' and specifying the resource 'HRMS session cookie'. It distinguishes itself from the sibling 'login_via_browser_capture' by describing manual cookie extraction via DevTools.

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?

Explicitly says only needed once, cookie persists across MCP restarts, and provides step-by-step instructions on how to obtain the cookie. It implies when to use this tool (first-time setup) versus potentially automated alternatives.

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