React Native MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'expert-level refactoring suggestions and implementations' which implies mutation/write operations, but doesn't disclose behavioral traits like whether changes are destructive, permission requirements, rate limits, or what the output format looks like. For a tool that likely modifies code, this is a significant gap in transparency.

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, efficient sentence that gets straight to the point: 'Provide expert-level refactoring suggestions and implementations'. Every word earns its place - 'expert-level' sets expectations, 'refactoring' specifies the action, 'suggestions and implementations' clarifies the output type. No wasted words or redundancy.

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 tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'implementations' means in practice (e.g., does it return modified code snippets?), doesn't address behavioral aspects like safety or permissions, and provides no usage context despite multiple sibling tools. The 100% schema coverage helps, but the description should do more for a mutation tool.

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 100%, so the schema already documents all 4 parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema (e.g., it doesn't explain what 'comprehensive' refactoring entails or how 'target_rn_version' affects suggestions). Baseline 3 is appropriate when schema does the heavy lifting.

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 states the tool's purpose: 'Provide expert-level refactoring suggestions and implementations' - a specific verb ('refactoring') with resource ('React Native component code' from schema). It distinguishes from siblings like 'analyze_component' or 'optimize_performance' by focusing on refactoring rather than analysis or optimization alone. However, it doesn't explicitly differentiate from 'remediate_code' which might overlap.

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 no guidance on when to use this tool versus alternatives. With siblings like 'analyze_component', 'optimize_performance', and 'remediate_code', there's no indication of when refactoring is preferred over analysis, optimization, or remediation. No prerequisites, exclusions, or comparative context are mentioned.

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