Apri login Amazon

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals that the browser is visible and that the user must manually enter password, MFA, and CAPTCHA, which is important context. However, it does not disclose what happens after login or whether the tool returns any status.

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 with no unnecessary words. Every element adds value: the visible browser, manual input, and specific credential types.

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 the tool's simple purpose (open a browser for login), the description covers the essential behavior and user interaction. However, it omits any mention of return values, completion signals, or follow-up steps like checking session status, which would improve completeness.

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 tool has zero parameters and an empty schema, so there is nothing to explain. The baseline for 0 parameters is 4, and the description appropriately avoids inventing parameter details.

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 function: it opens Amazon in a visible browser for manual login. The title 'Apri login Amazon' further specifies the login context, and the mention of password, MFA, and CAPTCHA distinguishes it from sibling tools like cart or search operations.

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 use when a manual login is needed (user personally enters credentials), but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like checking amazon_session_status first. The context is clear but without exclusions.

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