SapBrowserLogin

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

With no annotations, the description carries the full burden and does well: it discloses that Chrome is opened, that the flow is interactive, that any IDP works including 2FA, and that Basic Auth systems are unaffected. It stops short of stating whether the call blocks until the user finishes, how success/failure is signalled, or what happens if the browser is already open.

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 sentences, all load-bearing, with the core action front-loaded and the constraint ('Not needed for Basic Auth') placed last as an exclusion. No filler.

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?

No output schema and no annotations, so completeness rests on the description. It covers purpose, trigger conditions, mechanism, and exclusions; only the completion/interaction semantics (blocking, success signal, timeout) are unstated, which is a minor gap for a 1-param login trigger.

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 100% and the schema already documents systemId with examples ('DEV', 'PRD') and the active-system default. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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+resource: 'Trigger browser-based SSO authentication for an SAP system.' It also names the concrete mechanism (opens Chrome, interactive login) and enumerates supported IDPs, which cleanly separates it from the ABAP-object siblings in the list.

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?

Explicit when-to-use ('proactively authenticate before making requests, or to re-authenticate when SSO cookies expire') and an explicit when-not ('Not needed for systems using Basic Auth'). Nothing is left to inference.

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