login

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

Without annotations, the description transparently discloses behavior: opens visible window for manual login, polls up to wait_seconds for app shell, and persists the session. It omits details on timeout handling.

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, front-loaded with purpose. Every sentence adds value without redundancy.

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 simplicity, the description covers purpose, usage, parameter, and behavior. It does not mention error conditions, but is sufficiently complete for a straightforward login action.

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?

Schema coverage is 0%, but the description adds 'Polls up to `wait_seconds` for the app shell after you finish SSO / magic-link sign-in', explaining the parameter's purpose and how it affects behavior.

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 purpose: 'Open Slack in a visible window so you can log in manually.' It distinguishes from sibling tools like check_login (which checks status) and read tools that auto-open the window.

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 notes that read tools auto-open the window when signed out, making this tool optional. It provides context on when to use manually, but could be more explicit about specific scenarios.

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