login_user

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

With no annotations, the description must disclose behavioral traits. It mentions generating a new API key, which is a mutation. However, it does not disclose potential side effects such as invalidating previous keys, session management, or security implications. For a login tool, this lack of transparency could lead to misuse.

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 sentences, no wasted words. Front-loaded with the verb 'Login'. Highly concise and to the point.

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 no output schema and no annotations, the description should explain return values (e.g., API key) or side effects (session creation). It only says 'generate a new API key' but not how it's returned. Also missing error cases. Incomplete for a critical authentication 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 100% with descriptions for both email and password. The description adds no additional semantic meaning beyond what the schema provides. Baseline 3 is appropriate.

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 'Login with existing credentials and generate a new API key for MCP access.' This specifies the action (login) and the resource (existing credentials/API key). It distinguishes from siblings like register_user (new account) and change_password (password update).

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 says 'Use this if you already have an AI-Archive account but need to authenticate this MCP client.' This gives clear when-to-use context and implies not to use if you don't have an account. However, it doesn't explicitly mention alternatives like register_user.

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