cst_connect_tool

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

With no annotations, the description carries the full behavioral burden. It conveys that a launch may occur as a side effect, but does not disclose what happens on failure, which environment is targeted when several exist, whether the operation is idempotent, or any auth/timeout behavior.

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?

A single, front-loaded sentence with no filler. It earns its place, though the extreme brevity borders on under-specification for a session-establishing tool.

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 values need not be described, but with zero annotation coverage and 0% schema description coverage, the connection semantics (which environment, failure behavior, launch implications) are too thin for a tool that anchors the whole workflow.

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%, so the description must compensate and only does so partially. 'Optionally launching one' loosely maps to launch_if_needed, but 'pid' is never explained, and defaults/semantics are left to the schema alone.

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 (Connect) and resource (running CST Design Environment) plus an optional launch behavior. It is distinguishable from cst_quit_tool and cst_detect_tool, though it doesn't explicitly name a sibling to route against.

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?

No explicit when-to-use or when-not-to-use guidance. The phrase 'optionally launching one' hints that launch_if_needed exists but never says in which scenarios to prefer connecting over other session tools like cst_list_design_environments_tool.

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