adb_test_step

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

The description discloses the core actions (screenshot, logcat capture, saving to session directory) but lacks details on behavioral traits such as how steps are numbered, impact on logcat buffer, prerequisites like an active session, error handling, or performance implications. With no annotations, more transparency is expected.

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 a single, efficient sentence that front-loads the main action. It could be slightly improved by adding usage context or exclusions, but it is appropriately concise for the tool's simplicity.

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 does not explain numbering mechanisms, session prerequisites, return values (no output schema), or how steps relate to a test session. Given the tool's role in a likely multi-step workflow, this lack of context leaves gaps for an AI agent to correctly chain calls.

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 coverage is 100%, and parameter descriptions in the schema already explain each parameter's purpose. The tool description adds minimal additional meaning (e.g., 'numbered test step' context) beyond what the schema provides, so a 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 clearly states the tool captures a numbered test step by taking a screenshot and capturing logcat since the last step, saving both to the session directory. It effectively distinguishes from siblings like adb_screencap or adb_logcat by combining both actions in a step context.

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 usage within a test session (e.g., after adb_test_session_start) but does not explicitly state when to use this tool versus alternatives like separate screenshot or logcat tools. No exclusions or when-not-to-use guidance is provided.

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