react-native

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

With no annotations and a terse description, the tool's behavioral traits are almost entirely undisclosed. It does not mention whether actions are destructive, require specific permissions, or have side effects. The only hint is that it 'runs helpers', which is insufficient for an agent to predict consequences.

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 sentence, which is concise but overly brief. It lacks structure and does not front-load key information such as the tool's primary purpose or supported actions.

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 complexity (24 parameters) and lack of output schema, the description is incomplete. It does not explain what 'automation helpers' are, how the action parameter works, or what kind of results to expect. More context is needed for effective use.

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 high (96%), so the input schema already documents parameters effectively. The description adds no additional meaning beyond the schema, which is acceptable but not exceptional. Baseline score of 3 applies.

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. It does not specify what actions are supported beyond the single enum value 'dismiss-overlay', and it fails to distinguish the tool from sibling tools like click, swipe, or gesture which also perform automation actions.

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 alternatives. The sibling tools cover a wide range of specific actions, but the description offers no context for when to invoke react-native instead.

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