node_typecheck

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

With no annotations, the description carries the full behavioral burden. 'tsc --noEmit' is a meaningful disclosure: the tool performs a type check and does not emit compiled output. However, it does not explain failure behavior, exit codes, whether dependencies must be installed first, or what happens when type errors are found, leaving transparency partial.

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 sentence with no filler, and the key action is front-loaded immediately. Every word contributes: the operation, the target resource, and the command-line mode.

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?

The schema fully documents the parameters and the operation is simple, so an agent can invoke it with minimal risk. However, with no annotations, no output schema, and no usage-guidance context, some gaps remain around expected outcomes and when to prefer this over sibling tools. It is adequate but not comprehensive.

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 coverage is 100%, so the baseline applies since the schema already documents both projectPath and packageManager. The description adds no extra meaning beyond tying the action to a TypeScript project; it does not elaborate on path expectations, package-manager resolution, or edge cases.

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 specific verb ('Type check') and resource ('a TypeScript project'), and names the exact mechanism ('tsc --noEmit'). This clearly distinguishes it from sibling tools like build_project, compile_project, and node_test, because type-checking without emit is a distinct validation action.

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 given on when to choose this tool over its siblings, such as compile_project, node_test, or run_tests. The description implies its use only through the verb 'type check' and provides no exclusions, prerequisites, or alternative routing. An agent must infer usage context from the tool name and schema.

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