appium.create_session

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

No annotations are provided, so the description carries the full burden. It explicitly includes bracketed risk signals: '[approval required][device mutation][risk:dangerous]', which disclose approval needs, device-state mutation, and danger. It lacks detail on session cleanup or resource lifetime, but the key safety traits are surfaced.

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 two short sentences with no filler. The risk flags are front-loaded, and every clause adds distinct value: what the tool does and what input shape it expects.

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 description is adequate for a simple creation tool, and the risk flags cover approval and danger. But it omits the optional 'serverUrl' semantics, does not describe what the response returns (e.g., sessionId), and never mentions that the session should later be cleaned up with appium.delete_session. These are meaningful gaps given there is no output schema.

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 description adds real meaning for the 'capabilities' parameter by explaining it accepts W3C capabilities or a raw capabilities object, which is more than the schema's bare object type. However, 'serverUrl' is not mentioned in the description, and schema description coverage is 0%, so that parameter's semantics depend entirely on its self-explanatory name.

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 states a specific verb and resource: 'Create an Appium session.' It also clarifies the input form ('W3C capabilities or raw capabilities object'), which distinguishes it from session teardown tools like appium.delete_session. This is unambiguous and differentiating.

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 explains how to call the tool ('Pass W3C capabilities or raw capabilities object') but gives no guidance on when to use it, prerequisites such as an Appium server or device, or how it relates to alternatives like appium.delete_session or env.ensure_appium. An agent must infer the appropriate usage context.

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