SingleStore connections

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

readOnlyHint=true is consistent with merely opening a window, so no contradiction. The description adds genuinely useful behavioral context beyond the annotation: the result carries a ``browser_url`` and it should be surfaced as a clickable link under the app, which tells the agent what to expect and do after invoking.

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 short paragraphs, front-loaded with the core action, followed by the view identity and output-handling note. Reasonably tight, with only slight redundancy between 'Connections window' and 'Connections view of the SingleStore Workspace'.

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 parameterless window-opening tool with no output schema, the description covers what it opens, what it is, and the key return value handling (browser_url -> clickable link). Adequate; only explicit sibling differentiation is missing.

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, so the baseline is 4. There are no argument semantics to explain and the description correctly adds none.

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 ('Open') and resource ('the Connections window') and enumerates the capabilities it exposes (add, edit, test, switch connections). It does not explicitly distinguish itself from siblings such as connection_test or connection_activate, so the agent must infer that this opens a UI surface rather than performing an operation.

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 description implies usage (opening a connection-management window and posting the returned browser_url as a link) but never states when to pick this over alternatives like connection_test, connection_activate, or connections_state. Guidance is present but implicit.

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