rn_generate_project

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

No annotations exist, so the description carries the full burden of behavioral disclosure. 'Generate' implies file creation, but the description does not state whether existing files are overwritten, whether the tool invokes react-native init or similar commands, whether network access is required, or what the api_key is used for. An agent cannot predict side effects.

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?

Six words, front-loaded with the verb, zero filler or redundancy. It is efficiently sized, though the brevity borders on under-specification rather than being a concise rendering of richer content.

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 project-generation tool with two parameters, no annotations, and no output schema, a single sentence is inadequate. The description should explain what artifacts are produced, how api_key factors into generation, and whether re-running is safe. An agent is left guessing about the tool's effects and requirements.

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 only 50%: directory is documented as 'Project directory', but api_key has no schema description and no explanation in the tool description. The description adds nothing about parameters, so an agent cannot determine what api_key is for, whether it is required for generation, or what values it accepts.

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?

States a specific verb ('Generate') and resource ('React Native project structure'), clearly identifying the tool's domain and distinguishing it from non-RN generators. However, 'project structure' is somewhat ambiguous about what is actually created (directories only, or full scaffold?), and it does not differentiate from expo_generate_project, which also targets the React Native ecosystem.

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 gives no guidance on when to use this tool versus alternatives such as expo_generate_project, the various scaffold_* generators, or the rn_add_navigation/rn_add_state tools that extend an existing RN project. No prerequisites, exclusions, or workflow context (e.g., run this before rn_add_*) are provided.

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