Node Dev MCP Server

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

With no annotations, the description carries the full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this is a read-only or destructive operation, potential side effects (e.g., file modifications), permissions needed, or execution context (e.g., runs in a shell). This leaves critical behavioral aspects unclear for an agent.

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, straightforward sentence with zero waste. It's front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 (a build operation with 2 parameters), no annotations, no output schema, and incomplete schema coverage, the description is inadequate. It lacks details on what the tool returns, error conditions, or how it fits into the broader workflow with siblings, leaving significant gaps for an agent to understand its full context.

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 50% (only 'commitMessage' has a description). The description adds no parameter semantics beyond the schema, failing to explain 'currentWorkingDirectory' or clarify how parameters interact (e.g., if 'commitMessage' is used for git operations during the build). Baseline is 3 due to moderate schema coverage, but the description doesn't compensate for gaps.

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 'Run the build script in the workspace' clearly states the action (run) and target (build script), but it's vague about what 'build script' specifically entails compared to sibling tools like 'run_script' or 'install_dependencies'. It distinguishes somewhat by focusing on 'build' but lacks specificity about the script's nature or expected outcomes.

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?

No guidance is provided on when to use this tool versus alternatives like 'run_script', 'install_dependencies', or 'start_work'. The description implies it's for building, but it doesn't specify prerequisites (e.g., dependencies installed), exclusions, or contextual triggers, leaving usage ambiguous.

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