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 for behavioral disclosure. It states the tool analyzes for performance issues, implying a read-only diagnostic operation, but lacks details on execution time, resource requirements, output format, or potential side effects (e.g., whether it modifies files). For a code analysis tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes essential information, earning its place with zero waste.

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 complexity of codebase analysis, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the analysis entails, what output to expect (e.g., report, metrics, recommendations), or behavioral aspects like runtime or dependencies. For a tool with two parameters and no structured output, more context is needed to guide effective use.

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%, with clear descriptions for both parameters: 'codebase_path' and 'focus_areas' (including enum values). The description adds no additional parameter semantics beyond what's in the schema, such as format examples for the path or clarification on 'all' vs. specific areas. This meets the baseline of 3 since the schema adequately documents parameters, but the description doesn't enhance understanding.

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 action ('analyze') and resource ('entire React Native codebase for performance issues'), making the purpose immediately understandable. It distinguishes from some siblings like 'analyze_component' (component-level) and 'analyze_test_coverage' (testing focus), but doesn't explicitly differentiate from 'optimize_performance' which might be a related action. The specificity is good but could be slightly enhanced with sibling comparison.

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. It doesn't mention prerequisites, ideal scenarios, or contrast with siblings like 'analyze_codebase_comprehensive' (likely broader analysis) or 'optimize_performance' (which might be for implementing fixes). Without such context, the agent must infer usage from the name alone, which is insufficient for effective tool selection.

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