node_test

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

The description discloses that results are returned in structured form, which is useful behavioral information. However, with no annotations, it does not mention potential side effects such as coverage artifacts, prerequisites like installed dependencies, or failure behavior.

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?

Two tightly written sentences with the core action first and the return behavior second. There is no filler, repetition of schema fields, or unnecessary detail.

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 six-parameter tool with no annotations and no output schema, this description is too thin. It omits when to use this versus run_tests, what the structured results contain, and how framework/package-manager auto-detection behaves.

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?

The schema already describes all six parameters with 100% coverage, so the baseline is 3. The description adds little beyond the schema, and it only indirectly references the framework options.

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 uses a clear verb ('Run tests') and a specific resource ('Node.js/TypeScript project'), and narrows the scope to Jest, Vitest, or Mocha. It does not explicitly contrast itself with the generic sibling run_tests, so it stops short of full sibling differentiation.

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 Node.js/TypeScript scope and listed frameworks give implied guidance about when to use the tool. However, it does not explicitly explain when to choose it over the overlapping sibling run_tests or when not to use it.

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