login

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

No annotations provided; description covers credential persistence, interactive login, and force behavior. However, does not mention session validity detection or return value.

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?

Four sentences with main action front-loaded. Warnings are important but could be slightly more concise.

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?

Covers login flow and warnings, but does not describe output or what happens after success. Given interactive nature, still missing some context.

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?

Only parameter 'force' is explained with concrete use cases (re-auth/clear checkpoint), adding value beyond the schema's default value.

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?

Clearly states the verb 'Open and sign in' to resource 'Instagram via browser', distinguishing from sibling tools like login_status and logout.

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?

Explicitly says when to use (first login) and when to use force=True (re-auth/clear checkpoint). Provides warning about ToS risk. Lacks explicit when-not or alternatives.

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