react-native

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

No annotations exist, so the description carries the behavioral burden. It adds a 90s timeout and identifies the action as dismissing the RN dev overlay, which is useful. It does not disclose what happens when no overlay is present, whether the action is disruptive, or what a successful result looks like.

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 sentences convey the tool's scope, the concrete action, the condition for using it, and a timeout. It is front-loaded with the general purpose and specific use, with no filler.

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 one-action automation tool with a generous schema, the description covers the key trigger and the timeout. However, there is no output schema and no mention of return format, error conditions, or behavior when the overlay is absent, leaving an agent to guess at success/failure semantics.

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 94%, and the schema documents all 17 common parameters with descriptions and enums. The description adds no parameter-specific meaning, but the schema already provides the needed detail for the only action and selectors; baseline 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?

Description identifies the tool as handling React Native automation helpers and specifically names the dismiss-overlay action with its purpose: closing a visible development error overlay. Without inspecting the schema, an agent can infer what invocation achieves. It is not fully distinguished from sibling tools, but its specific use case is clear.

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?

Description states when to use it: after a development error overlay appears, before continuing normal UI automation. It does not name alternative tools or exclusions, but the tool's single action and targeted condition make the usage context reasonably unambiguous.

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