React Native MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves - whether it generates recommendations, provides examples, returns structured advice, or offers implementation guidance. For a tool with no annotation coverage that provides architectural advice, this is a significant gap in behavioral 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 extremely concise - a single sentence that clearly states the tool's purpose without any wasted words. It's front-loaded with the core functionality and doesn't include unnecessary elaboration. This is an excellent example of efficient communication.

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 purpose (providing architectural advice), no output schema, and no annotations, the description is minimally adequate but lacks important context. It doesn't indicate what form the advice takes (text recommendations, diagrams, best practices), whether it's tailored to the input parameters, or what level of detail to expect. For a tool that presumably generates complex output, this is a significant gap.

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 doesn't add any parameter semantics beyond what's in the schema - it doesn't explain how 'project_type' influences the advice or what types of 'features' are most relevant for architectural decisions. With complete schema coverage, the baseline 3 is appropriate.

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 as 'Get React Native architecture and project structure advice' - a specific verb ('Get') and resource ('React Native architecture and project structure advice'). It distinguishes from siblings like 'analyze_codebase_comprehensive' or 'optimize_performance' by focusing specifically on architectural guidance rather than analysis or optimization. However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

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 when this tool is appropriate versus using 'analyze_codebase_comprehensive' for broader analysis or 'optimize_performance' for performance-focused advice. There's no context about prerequisites, timing, or exclusions for using this architectural advice tool.

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