atlassian-browser-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: it launches a visible browser (indicating a UI-based, interactive process), waits for manual input (implying user involvement and potential delays), and handles SSO/MFA (specifying authentication methods). However, it lacks details on error handling, timeouts, or post-login state.

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 a single, front-loaded sentence that efficiently conveys the core functionality without waste. Every word ('Launch', 'visible browser', 'wait', 'manual SSO / MFA login') adds value, making it appropriately sized and well-structured for quick understanding.

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 complexity (interactive authentication), no annotations, and an output schema (which handles return values), the description is mostly complete. It covers the main behavioral aspects but could improve by addressing prerequisites (e.g., browser availability) or post-execution states, keeping it from a perfect score.

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 description coverage is 0%, so the description must compensate. It does not mention parameters at all, but the tool has only 2 parameters with defaults and enums, making the baseline high. The description's focus on the login process implicitly relates to 'target' and 'url', but no explicit parameter guidance is given, slightly reducing the score from a perfect 5.

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 action ('Launch a visible browser and wait for manual SSO / MFA login'), specifying the verb ('Launch'), resource ('browser'), and scope ('manual SSO / MFA login'). It distinguishes from sibling tools (e.g., 'jira_login' or 'confluence_login' are absent), making the purpose explicit and unique.

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 usage for authentication scenarios requiring manual intervention (SSO/MFA), but does not explicitly state when to use this tool versus alternatives (e.g., automated login methods or other auth tools). No exclusions or prerequisites are mentioned, leaving usage context partially inferred.

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