Check Amazon.in login status

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

No annotations provided, so description carries full burden. Describes loading homepage and reporting status, mentions persistent session, but lacks details on side effects (e.g., navigation, session initialization) and return format.

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 concise sentences: first describes action and output, second provides actionable next step. No wasted words, front-loaded.

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 zero-parameter tool with no output schema, description covers purpose and likely outputs (signed-in, CAPTCHA, sign-in wall). Lacks detail on error cases or exact return structure, but adequate for the simple task.

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 and schema coverage is 100%. Description adds no parameter info as none needed. Baseline 3 per rules.

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 checks login status by loading Amazon.in homepage and reports sign-in, CAPTCHA, or sign-in wall. It distinguishes from sibling 'login' tool but not explicitly from 'get_browser_state' or 'finish_login'.

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 guidance to run 'npm run login' if not signed in, implying use this tool before acting. Does not explicitly state when not to use or compare with siblings like 'get_browser_state'.

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