login

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

With no annotations, the description carries the burden of disclosure. It reveals the behavioral trait of attempting stored cookies before prompting for credentials, but does not describe session side effects, failure modes, or whether a session is established.

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 two sentences with no waste, front-loading the primary action and adding a useful detail about cookie-first behavior.

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?

The description covers the core login flow and parameter options, and the schema is complete. However, it lacks information about return values or session state, which could be important for an agent to proceed, but given the simple nature of login, it is adequate.

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 all four parameters. The description adds context by explaining that email/password are optional because stored cookies may suffice, and that 2FA is handled via a TOTP code, enhancing the schema's basic descriptions.

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 logs into LinkedIn with credentials and optional 2FA, and mentions the cookie-first behavior. This distinguishes it from sibling tools like set_cookies or open_manual_browser, which serve different purposes.

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 implies usage for authentication and indicates that stored cookies are tried first, giving context for when credentials may not be needed. However, it does not explicitly mention alternatives or exclusions, such as using open_manual_browser for manual login.

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