react-native

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

No annotations are present, so the description must fully disclose behavior. It only states 'run helpers,' omitting details about side effects, prerequisites (e.g., device session), or whether it modifies app state. The 'action' parameter hints at commands but is not explained.

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 only one sentence, which is concise but lacks necessary information. It sacrifices clarity for brevity. A slightly longer description that clarifies purpose and usage would improve without being verbose.

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 22 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the tool's overall goal, how parameters interrelate, or expected outputs. The complexity demands a more comprehensive description to avoid agent confusion.

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 description coverage is 95%, so the input schema already documents parameters well. The description adds no extra meaning beyond 'automation helpers,' which does little to clarify parameter usage. Baseline 3 is appropriate since schema carries the load.

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 'Run supported React Native app automation helpers' is vague and does not specify what the tool itself does. It fails to distinguish from sibling tools like click, swipe, which are specific actions. The tool appears to be a generic dispatcher based on the 'action' parameter, but this is not clearly stated.

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?

No guidance is provided on when to use this tool versus sibling tools. The description does not mention that this tool is a runner for helpers, which could be used for more complex or aggregated actions, leaving the agent without decision support.

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