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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds real value beyond them: it discloses that the result is a browser handoff rather than a direct connection, and it explicitly commits that OAuth secrets, cookies and passwords are never collected in chat. It stops short of saying what the handoff payload contains or what completes the flow.

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?

Two tight sentences with the capability front-loaded and the security constraint following. No filler, no redundancy, and nothing that could be cut without losing information.

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?

An output schema exists, so return-value details are rightly omitted, and annotations already declare the mutating/open-world nature. The description supplies the remaining agent-critical facts: the two supported platforms, the browser-handoff mechanism, and the no-credential-in-chat guarantee.

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 50%: workspaceId carries a thorough schema description covering key types and the multi-workspace error case, while platform is an undocumented enum. The description's "LinkedIn or Google" merely restates the enum values and adds nothing to workspaceId semantics, so it neither compensates for the gap nor falls below the baseline for this coverage level.

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 ("return a browser handoff") and resource ("connecting a new LinkedIn or Google account"), which is much more precise than the bare title. It scopes to NEW connections, implicitly separating it from campaignstack_get_accounts or edit_workspace_accounts, though it never names those siblings directly.

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?

Usage is only implied: the word "new" suggests this is for onboarding an additional account rather than editing an existing one, steering the agent away from edit_workspace_accounts. There is no explicit when-to-use statement, no prerequisites, and no named alternative.

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