Sign in to Amazon.in (opens a window)

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

Discloses that it opens a visible window, keeps it open, and saves session automatically. Without annotations, it covers key behavioral traits, though it could mention behavior if already signed in.

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?

Three concise sentences with no wasted words. Purpose is front-loaded and action-oriented.

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?

Adequately explains the login flow, session handling, and post-login step. Could clarify behavior in edge cases like already being signed in, but overall sufficient for a 0-param 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?

No parameters exist, so schema coverage is 100%. Description adds no parameter info, which is acceptable given absence of parameters.

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 opens a visible Chrome window at Amazon.in sign-in page for manual sign-in, distinguishing it from command-line login and specifying the follow-up tool.

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?

Provides clear context for when to use (manual sign-in with OTP/CAPTCHA) and instructs to call finish_login after. Lacks explicit when-not-to-use vs sibling tools like login_status, but effectively guides manual flow.

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