qlikcloud_login

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

With no annotations provided, the description carries the full burden of disclosing side effects. It clearly states that the tool opens the user's browser, shows a consent screen, and that subsequent actions use the user's identity and permissions. It also explains the behavior of 'force' and 'switch_account', including that switch_account implies force.

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 appropriately concise while covering essential behavior. Every sentence contributes meaningful information: the core action, side effects, usage triggers, and parameter explanations. There is minimal redundancy, and the structure with an Args section improves readability.

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 login tool with two optional boolean parameters, the description is complete. It explains the action, the side effects, the conditions for use, and the meaning of both parameters. The output schema is not shown, but for a login flow the return value is secondary; the description provides enough context for correct invocation.

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 JSON schema provides only names and defaults with no descriptions, so the description must compensate. The Args section explicitly explains both parameters: 'force' means sign in again even if a session exists, and 'switch_account' means re-authenticate as a different account and implies force. This fully covers the parameter semantics.

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: 'Sign in to Qlik Cloud as yourself, in your browser.' It identifies the specific resource (Qlik Cloud) and the action (login), and it is obviously distinct from sibling tools like logout, health, and delete.

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 provides explicit usage conditions: 'Call this when a tool says you are not signed in, or when the user asks to sign in or switch accounts.' It also warns against speculative calls because it opens a browser window, giving clear guidance on when not to use it.

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