connection_sso_sign_in

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

Annotations only tell the agent this is non-read-only and non-destructive. The description adds real behavioral context beyond that: it opens a page in the user's browser (interactive, requires user presence) and blocks waiting for a token with a stated 2-minute timeout. That is valuable for an agent deciding whether to call it synchronously.

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?

One sentence, front-loaded with the action and scope, then the mechanism and timeout. No wasted words; every clause earns its place.

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 no-output-schema tool the description covers action, mechanism, and timeout, which is decent. It omits prerequisites (does the connection need to exist/be activated first?), what the token result looks like, and failure modes (timeout behavior).

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% and the sole required parameter 'name' carries no description. The description does not clarify whether 'name' is the connection name, the SSO provider, or something else, so it fails to compensate for the schema gap.

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?

States a specific verb (browser sign-in) and resource (SSO connections), and narrows scope to Helios or Microsoft Entra ID. It does not explicitly contrast with sibling sign-in tools like sas_viya_sign_in or connection_activate, so sibling differentiation is only partial.

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 parenthetical 'for SSO connections (Helios or Microsoft Entra ID)' implies when this applies, but there is no explicit when-to-use/when-not guidance and no named alternative for non-SSO connections (e.g., connection_activate). Usage is inferred rather than stated.

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