App Connector: Disconnect

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

The description adds behavior beyond the annotations by stating "Mutates session state (tears down the connection)" and clarifying idempotence: "closing an already-closed session is a no-op." These details complement the idempotentHint and readOnlyHint annotations rather than merely repeating them.

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 dense sentences with no filler. It front-loads the main action, then adds behavioral nuance, then gives usage context. Every sentence contributes distinct value.

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-optional-parameter tool, the description combined with the annotations covers the purpose, side effects, idempotence, and when to call it. Nothing essential is missing for an agent to select and invoke it correctly.

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 documents the only parameter, device, with 100% coverage, including that it is optional and what happens if omitted. The description does not add further parameter-specific meaning, so the baseline score 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 opens with a specific verb and resource: "Close the RALE / App Connector session on the targeted device." This clearly distinguishes it from sibling connect/disconnect tools such as app_connector_connect and telnet_disconnect by naming the exact session type.

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?

It gives explicit triggers: "Use it to free the session or force a clean reconnect." It also provides useful when-not guidance: "normal RALE tools do not require you to disconnect between calls." However, it does not explicitly name alternative disconnect tools or state when to use telnet_disconnect instead, so it stops short of full routing guidance.

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