App Connector: Connect

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

The description states the tool is 'idempotent — reconnecting an open session is a no-op', but the annotations declare idempotentHint: false. This is a direct contradiction about a key behavioral trait. The description does add useful context about session-state mutation and auto-connect, but the contradiction makes the transparency unreliable.

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 compact, front-loaded with the core purpose, and every sentence adds value: what it does, side-effect behavior, auto-connect context, and when to call it explicitly. No filler or repetition of schema fields.

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 one-optional-parameter connection tool with no output schema, the description covers purpose, side effects, and usage context well. It loses one point because the idempotency claim conflicts with the annotation, which could mislead an agent reasoning about call safety and retry behavior.

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 100% description coverage for the single parameter 'device', including the omit-to-use-focused-tab guidance. The description does not add further parameter-level detail, but the schema already handles it, so the baseline of 3 is appropriate.

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 action ('Open a RALE / App Connector session'), the target ('the device's running Dev App'), and distinguishes this tool from siblings by noting it is rarely needed explicitly because other tools auto-connect. This gives an agent a precise sense of the operation and its place among related tools.

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 explicitly says when to use the tool ('to pre-warm the session or surface connection errors early') and, more importantly, when not to use it ('You rarely need to call this explicitly') while naming the alternatives that auto-connect. This is strong routing guidance.

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