init

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 that the tool resets AI's Next.js knowledge baseline, enforces a documentation-first approach, and documents available tools. It does not mention any side effects or destructive actions, but the described behaviors are non-destructive and well-explained.

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 fairly long and uses formatting (bold, emoji, bullet points) which aids readability. However, it is somewhat verbose and repeats the importance of calling it first. It is structured well but 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 the simplicity of the tool (one optional param, no output schema), the description explains the overall purpose and usage well but fails to describe the single parameter. Without the parameter explanation, the description is incomplete for an AI to correctly invoke the tool with appropriate input.

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 has one parameter (project_path) with 0% schema description coverage, and the description does not mention this parameter at all. It adds no meaning beyond what the schema provides (just a name and type). For a single-parameter tool, this is a significant gap.

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 that init initializes the Next.js DevTools MCP context and establishes mandatory documentation requirements. It uses a strong verb ('Initialize') and specifies the resource ('Next.js DevTools MCP context'). The warning 'CALL THIS FIRST' distinguishes it from sibling tools that have different purposes.

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 explicitly instructs that this must be called at the start of every Next.js session and provides a list of what it does. It gives clear when-to-use guidance, though it doesn't explicitly mention when not to use or alternatives.

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