adb_regression_baseline

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

No annotations are provided, so the description must carry the burden. It discloses that the tool captures multiple performance metrics and saves a file, but doesn't mention potential side effects (e.g., impact on device performance during capture, permission requirements).

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: first sentence states the action and scope, second sentence explains the output and relationship to sibling tool. No redundant words, front-loaded with key information.

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 complexity (multiple metrics) and lack of output schema, the description adequately covers what is captured and the purpose. It could be improved by stating where the JSON file is saved, but it is largely complete for the agent's decision-making.

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 input schema has 100% description coverage for all three parameters. The description adds marginal value by providing examples for the 'label' parameter (e.g., 'before-refactor'), but otherwise the schema already conveys the meaning.

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 it captures a performance baseline for a package, listing specific metrics (memory, CPU, frame stats, battery, network) and explains the output (timestamped JSON file). It also names the sibling tool adb_regression_check for comparison.

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 explicitly mentions the created JSON file is for later comparison with adb_regression_check, indicating when to use this tool. It does not provide explicit when-not-to-use guidance, but the context is clear.

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