rtt_connect

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

The description does not disclose behavioral traits beyond the bare action of connecting. With no annotations, the agent is left uninformed about side effects, persistence of the connection, or required setup. A 2 reflects the significant gap for a connection-oriented tool.

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 description is a single, concise sentence that delivers the core purpose with no extraneous words. It is optimally short for the complexity level.

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?

Given the tool's role in a suite of RTT and debugging tools, the description is too sparse to provide complete context. It does not explain what RTT is, what the connection implies, or how it relates to other tools (e.g., rtt_read, rtt_send). The agent may need to infer meaning from the sibling tool names.

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 input schema has zero parameters with 100% coverage, so the description does not need to add parameter details. The description is adequate for a parameterless tool, earning a baseline 4.

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 uses a clear verb+resource structure: 'Connect to RTT'. It distinguishes from sibling RTT tools (e.g., rtt_clear, rtt_disconnect) by indicating it establishes a connection. However, the acronym RTT is not expanded, which may be ambiguous without domain knowledge.

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 guidance is provided on when to use this tool versus alternatives like gdb_connect or telnet_proxy_start. There is no mention of prerequisites, ordering, or situations where the tool is inappropriate.

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