delete_session

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

The description states the tool ends the session and closes the app, which is the core destructive behavior. While annotations already declare destructiveHint=true, the description adds important context about the autonomous use prohibition, which is beyond what annotations provide.

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 sentences: the first describes what the tool does, and the second provides usage guidelines. It is front-loaded and efficient, though the second sentence could be slightly more concise.

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?

Given no parameters, no output schema, and annotations providing destructiveness, the description is complete. It does not need to explain return values or parameters, and it provides all necessary behavioral and usage context.

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?

There are no parameters, so the description naturally has nothing to add about parameters. With 100% schema coverage (trivially), a baseline of 4 applies due to no param info being needed.

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 tool ends the current Appium session and closes the app, using specific verbs ('End', 'close') and resources ('Appium session', 'app'). It distinguishes itself from siblings by its destructive nature, unlike many other session or element 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 provides explicit guidelines: 'Only call this when the user explicitly asks to stop or end the session' and 'Never call autonomously — always confirm with the user before terminating.' This clearly tells the agent when to use and when not to use the tool.

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