init

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

No annotations provided, so description carries full burden. It discloses behavioral traits like resetting AI knowledge and enforcing documentation-first approach, but does not mention potential side effects like state persistence or permissions.

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 front-loaded with an important warning and uses bullet points for structure, but contains some redundant phrasing (e.g., repeating 'mandatory' multiple times). Could be more concise.

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 no output schema and one parameter, the description covers purpose and usage adequately but lacks parameter documentation. It is reasonably complete for its intended init role.

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?

Input schema has one parameter (project_path) with 0% description coverage. The description does not explain the parameter's purpose or format, leaving the agent without guidance on what value to provide.

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 initializes Next.js DevTools MCP context and establishes mandatory documentation requirements. It specifies a specific verb ('Initialize') and resource ('Next.js DevTools MCP context'), and distinguishes itself from siblings by being the setup tool that must be called first.

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?

Explicitly states 'CALL THIS FIRST' and 'MUST be called at the START of every Next.js development session', giving clear when-to-use context. It lists use cases but does not provide when-not-to-use or alternatives, assuming it is unique.

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