connect_to_session

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

With no annotations, the description carries the behavioral burden and does so well: it reveals that the tool may attach to an existing session or create a new Appium session, a side-effectful action. It stops short of describing failure modes or what happens when create_if_needed=false and no session exists.

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 and scannable: one intro sentence, three behavior bullets, and an Args list. No filler, and the most important branching logic is front-loaded.

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?

The tool is a moderately complex connection helper with three optional parameters and an output schema to describe the return value. The description covers the main behavior and parameter semantics, but omits the no-session/no-create edge case and error conditions.

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?

Schema description coverage is 0%, so the Args section is the only source of parameter meaning. It clearly explains appium_url, session_id, and create_if_needed, though it leaves the create_if_needed=false/no-active-session case implicit.

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 action and resource: 'Se connecte à un serveur Appium'. The conditional bullets (attach to provided session, find active, create if needed) make the tool's role unmistakable and distinguish it from siblings like get_page_source, tap_element, or close_session.

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 gives clear selection context: it is the session setup operation, and it states the branches for session_id, active-session discovery, and create_if_needed. It does not explicitly mention when not to use it or name alternative connection tools, but among the sibling set it is the only connection entry point.

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