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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real behavior beyond that: the browser is the user's signed-in real Chrome, the URL takes over the site's existing tab rather than spawning one, and the call returns the in-view elements and text. Only finer details like failure modes when a session is already live are omitted.

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 definition is front-loaded with the core action and the ordering rule before any detail, and most sentences carry actionable content. The trailing enumeration of six Sprout Social actions is the one heavier block, though it does serve as routing context for the agent.

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?

There is no output schema, and the description compensates by describing what comes back (elements and text in view, with matching numbers). For a two-parameter, zero-required, open-world session-start tool, that is close to sufficient; only ambiguity around the 'same numbers' reference and re-invocation semantics keeps it below a 5.

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 100%, so the baseline is 3; the description goes beyond the schema by explaining how `url` is routed (site's open tab first, else a new tab, preserving the user's own tabs), which the format:'uri' field cannot convey. It adds nothing about `app` beyond what the schema description already states, keeping it from a 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 gives a specific verb pair ('starts' the Cloud Browser, 'opens' the url) and names the resource precisely as the user's real Chrome on Cotlet. It also distinguishes itself from the many sibling browser tools with the imperative 'Call it first', so an agent knows this is the session-initializing call rather than a navigation or read step.

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?

Sequencing guidance is explicit and front-loaded: 'Call it first.' The description also names the downstream domain (Sprout Social actions this serves) so an agent can see which tasks route through it. It stops short of stating when-not to use it (e.g., versus cotlet_browser_navigate when a session already exists), leaving that inference to the 'first' cue.

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