App Connector: Connect

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

The description goes beyond the annotations by explaining that the tool mutates session state, is idempotent with reconnection being a no-op, and that other tools auto-connect on demand. It adds useful behavioral context without contradicting the provided readOnlyHint, openWorldHint, idempotentHint, or destructiveHint annotations.

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 three tightly written sentences with no filler: it front-loads the purpose, then covers side effects and idempotency, then gives usage guidance. Every sentence contributes distinct information.

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 simple one-parameter connect tool with rich annotations and no output schema, the description covers purpose, side effects, idempotency, auto-connect behavior, and explicit usage conditions. An agent has enough context to decide when to call it and what it does.

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 schema already provides full coverage for the single optional 'device' parameter, including the behavior of omitting it (uses the focused Dev Studio tab). The description does not add param-level details, but none are needed given the schema's completeness.

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 opens with a specific verb and resource: 'Open a RALE / App Connector session against the device's running Dev App.' It clearly identifies what the tool does and implicitly distinguishes it from connection-disconnect and command-execution siblings such as app_connector_disconnect and rale_command.

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?

Usage guidance is explicit and practical: it says the tool is rarely needed because rale_command, app_function, and rale_get_node_by_id auto-connect on demand, and it states the only recommended uses are pre-warming the session or surfacing connection errors early. This gives clear when-to-use and when-not-to-use direction.

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