login_help

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get help and troubleshooting tips' suggests a read-only, informational operation, it doesn't clarify what form the help takes (text, links, step-by-step guidance), whether it requires authentication, if it has rate limits, or what happens when the optional email parameter is provided. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized for a simple help tool and front-loads the essential information. Every word 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?

For a simple informational tool with one optional parameter and no output schema, the description is minimally adequate. However, given the lack of annotations and the presence of multiple sibling tools addressing similar login concerns, the description should do more to clarify this tool's specific role and what kind of help it provides versus alternatives.

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 description provides no parameter information, but the input schema has 100% description coverage with a single optional 'email' parameter clearly documented as 'Your email address (optional, for personalized help)'. With high schema coverage and only one parameter, the baseline score of 3 is appropriate - the schema does the heavy lifting, and the description doesn't add value beyond what's already in the structured data.

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 as 'Get help and troubleshooting tips for N Lobby login' - a specific verb ('Get help and troubleshooting tips') applied to a specific resource ('N Lobby login'). However, it doesn't distinguish this tool from potential alternatives like 'debug_connection' or 'verify_authentication' among the sibling tools, which might also address login issues.

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. With sibling tools like 'debug_connection', 'verify_authentication', and 'interactive_login' that might address similar login-related concerns, there's no indication of when this help-focused tool is preferable versus when those diagnostic or action-oriented tools should be used instead.

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