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 the full burden. It mentions analysis types but doesn't disclose behavioral traits like whether this is a read-only operation, what permissions are needed, whether it modifies the codebase, execution time, output format, or error handling. For a comprehensive analysis tool with zero annotation coverage, this leaves significant 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 a single, efficient sentence that front-loads the key information ('comprehensive React Native codebase analysis') followed by specific analysis types. Every word contributes to understanding the tool's scope, though it could be slightly more structured (e.g., separating core purpose from details).

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 (comprehensive analysis with multiple types), lack of annotations, and no output schema, the description is incomplete. It doesn't address what the analysis returns, how results are presented, whether it's safe to run, or how it differs behaviorally from siblings. More context is needed for effective agent 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%, so the schema already documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain what 'all' means in analysis_types or provide examples of codebase_path formats). Baseline 3 is appropriate when the 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 performs 'comprehensive React Native codebase analysis' with specific analysis types listed (performance, security, refactoring, upgrades). It distinguishes itself from more focused sibling tools like 'analyze_codebase_performance' or 'analyze_test_coverage' by emphasizing comprehensiveness. However, it doesn't specify the exact verb or output format.

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 implies usage for comprehensive analysis needs through the word 'comprehensive' and the list of analysis types. However, it doesn't explicitly state when to use this vs. more specific sibling tools like 'analyze_codebase_performance' or 'refactor_component', nor does it mention prerequisites or exclusions.

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