adb_test_session_start

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 mentions creating a directory but doesn't disclose potential side effects (e.g., if directory exists, whether it overwrites, or any restrictions on session names). More detail on behavioral traits beyond creation would be beneficial.

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 with no filler. It front-loads the main action and then explains the outcome efficiently. Every sentence adds 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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description is adequate but not complete. It doesn't mention the return value or that the session must be ended with adb_test_session_end. Including a pointer to the counterpart would improve completeness.

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 descriptions for both parameters (100% coverage). The description adds the context of structuring test sessions, which relates to the name parameter. However, it doesn't add new meaning beyond what the schema provides, so the baseline 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 clearly states the purpose: 'Start a structured test session' and explains what it does: 'Creates a named directory for organizing numbered screenshots and logcat captures.' This is specific with verb and resource, and it naturally distinguishes from sibling tools like adb_logcat_start or adb_screencap.

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 implies it should be used before test steps that generate screenshots or logcat, but it doesn't explicitly state when to use or when not to use. No mention of alternatives or prerequisites, such as needing to end the session with adb_test_session_end.

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