load_js_project

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context (ts-morph, deterministic, framework detection) but does not disclose side effects like state persistence, whether multiple loads are allowed, or the need to unload. This is a notable gap for a state-changing tool.

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 concise sentences with no fluff. The primary action and purpose are front-loaded, and the framework list adds value without unnecessary length.

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?

There is no output schema, and the description does not explain return values or behavior on invalid paths. It also does not explicitly state that loading is a prerequisite for other analysis tools, which is important given the large sibling set. The tool is simple enough that this is adequate but not complete.

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%, with both 'source' and 'alias' fully described. The description adds no extra meaning beyond noting the project directory, so 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 loads a JavaScript/TypeScript project directory for deterministic analysis using ts-morph, and lists the frameworks it detects. This distinctly identifies it as the entry-point loading tool among many analysis 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 phrase 'for deterministic analysis' implies this should be used before other analysis tools, but it does not explicitly name alternatives or exclusions (e.g., detect_framework, refresh_js_project, unload_js_project). Context is clear but not fully explicit.

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