metro

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully reveals the session-binding lifecycle and clearing behavior, but it doesn't describe side effects of reloading, failure modes, or prerequisites, leaving some gaps.

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 three dense sentences, front-loaded with the main purpose and no filler. Each sentence adds distinct behavioral information that is worth keeping.

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—44 parameters, no output schema, and no annotations—the description provides the core flow and binding behavior but omits response details, operational prerequisites, and context about what happens on reload. It is adequate but not fully 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?

The description only generically refers to 'explicit runtime inputs' and provides no mapping to the 44 parameters. Schema coverage is 52%, and the description does not compensate for undocumented parameters, so it adds minimal parameter-level 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 identifies the tool's function: prepare a React Native development server or reload connected apps. It gives specific verbs and a resource, and the session-binding nuance distinguishes it from generic React Native tooling.

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?

It explains that the tool uses the session-bound development server and instructs when to provide explicit runtime inputs to override the binding. This gives clear usage context, though it doesn't name alternative tools or explicitly state when not to use it.

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