rn_add_navigation

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only restates the action of adding setup and gives no indication of side effects such as file modifications, dependency changes, or whether existing navigation configuration will be overwritten. The unexplained api_key parameter makes the lack of behavioral context even more problematic.

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 short sentence with no wasted words, which is concise and front-loaded. It sacrifices substance for brevity, but conciseness itself is handled well. The structural problem is not bloat but under-specification, which is more appropriately penalized in other dimensions.

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?

With no annotations, no output schema, one undocumented parameter, and no mention of prerequisites, side effects, or project state, the description is far from complete. A tool that mutates a project's navigation setup needs at least a note on what files/dependencies are affected and whether this targets an existing React Native project. The information gap is severe even for a tool with only two parameters.

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 input schema documents directory as 'Project directory', but the description adds no meaning for either parameter and completely ignores api_key. With schema description coverage at only 50%, the description should at least clarify what api_key is for and when it is required. No parameter-level guidance is provided beyond what the schema already states.

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 a verb ('Add') and a specific resource ('React Navigation'), so it is not a mere tautology. However, 'setup' is vague: it does not say whether the tool installs dependencies, creates navigators, configures a container, or modifies existing navigation code. It also provides no differentiation from nearby sibling tools like rn_add_state or rn_generate_project.

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?

There is no guidance on when to use this tool, what prerequisites are required, or what alternatives should be considered. An agent cannot tell from the description whether this is meant for a fresh project, an existing React Native app, or a project already using some navigation solution. The sibling list provides context, but the description itself does not.

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