connect_simulator

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

With no annotations provided, the description carries the full burden but fails to disclose idempotency, error conditions, state persistence, or side effects of establishing the connection.

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?

Well-structured docstring format with purpose front-loaded and efficient Args section. No redundant text, though slightly informal formatting.

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?

Adequate for a connection tool with output schema present (excusing return value documentation), but lacks critical behavioral context regarding connection state management and error handling.

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?

Effectively compensates for 0% schema description coverage by documenting all three parameters (host, port, timeout) with meaningful semantics, including usage hints and default values.

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 clearly states the specific action (Connect) and target resource (SimVision instance running mcp_bridge.tcl), distinguishing it from sibling tools like disconnect_simulator or sim_run.

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?

Provides operational context for the host parameter (SSH tunnel recommendation), but lacks explicit guidance on when to use this tool versus disconnect_simulator or prerequisites for other simulator operations.

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