react-native

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 only says dismiss-overlay 'close[s] a visible development error overlay' but does not disclose behavior when no overlay is present, waiting time, side effects, or error handling. This is a significant gap for a tool with zero annotation coverage.

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?

Two concise sentences with no redundancy. The first sentence names the tool's category, the second provides a specific use case. Every word earns its place.

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?

For a simple one-action tool, the description gives the essential use case but omits return behavior, error conditions, and edge cases. Since there is no output schema, the description should at least mention what happens if the overlay is not present or if the action fails. Adequate but not complete.

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 96%, so the baseline is 3. The description adds no parameter meaning beyond the schema; it only maps to the action enum. The schema already explains all parameters, so the description does not need to compensate.

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 states the tool runs React Native automation helpers and specifically identifies the dismiss-overlay action to close a visible development error overlay. This is a clear verb+resource combination, though the phrase 'supported React Native automation helpers' is a bit generic and does not fully distinguish from potential sibling automation tools.

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 provides explicit context: use dismiss-overlay when a development error overlay is visible, and do so before continuing normal UI automation. It does not mention alternatives or exclusions, but the use case is specific and easily actionable.

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