conf_browser_login

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. Beyond that the description adds nothing: it doesn't say whether the call blocks until the user completes SSO, whether it returns a URL or a status, how failure/timeout behaves, or that a human must interact with the browser — all material for an open-world, side-effecting UI action. No contradiction with readOnlyHint (no Confluence data is modified), but disclosure is thin.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is also the source of the missing behavioral detail rather than a sign of tight editing.

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 an interactive SSO trigger with no output schema and no parameters, the description should explain the interaction model (blocking vs. non-blocking, human-in-the-loop, what to do after) and its relationship to conf_browser_auth_status. None of that is present, leaving the agent to guess how to sequence the call.

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 takes zero parameters and the empty object schema is exhaustive, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the call needs no arguments.

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 pairs a specific verb ("Open browser") with a specific resource/flow ("Confluence SSO sign-in"), so an agent immediately knows this initiates an interactive sign-in rather than a data query. It does not, however, mention the closely related sibling conf_browser_auth_status, which is the natural companion tool for checking whether sign-in is needed or succeeded.

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?

There is no explicit when-to-use guidance, no statement of prerequisites (a browser-capable environment, human interaction), and no pointer to conf_browser_auth_status for verifying state afterward. Usage is only implied by the name and the word "sign-in".

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