node_build

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 discloses the package managers but not whether dependencies are installed first, what side effects occur (e.g., output artifacts), what the return behavior is, or whether the operation is safe. For a build operation, this is a meaningful transparency gap.

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, well-constructed sentence with no filler. It front-loads the core action and resource, and every word earns its place.

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?

With no annotations or output schema, the description is moderately complete: it identifies the operation and package managers, and the schema covers parameters. However, it omits context about whether a specific script must exist, whether installation happens first, and what success/failure looks like, so an agent may still need to probe behavior.

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 parameters are already documented. The description adds a little extra meaning by reaffirming the accepted package managers (npm, pnpm, yarn) and the Node.js/TypeScript context, but it does not go beyond what the schema already conveys.

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 verb ('Build') and resource ('Node.js/TypeScript project'), and names the supported package managers. It is distinguishable from siblings like set_java_version or node_test by its language and build focus, but it does not explicitly contrast itself with the more generic build_project or compile_project siblings.

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 gives no guidance about when to choose this tool over build_project, compile_project, or install_project. It implies usage for Node.js/TypeScript builds but never states exclusions or alternatives, leaving the agent to infer selection criteria from the tool name alone.

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