nextjs_docs

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

With no annotations, the description carries full burden. It clearly states the tool does not fetch documentation but locates it, explains where docs are stored, and mentions upgrade guidance. This gives good transparency, though it could explicitly state it's read-only with no side effects.

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 well-structured with a clear first sentence stating purpose, then clarifying behavior, then usage guidance. It is concise with no filler, though it could be slightly tightened without losing clarity.

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 description covers the main purpose and usage but lacks details on output format (what exactly is returned, e.g., a path, a list) and error handling. Since no output schema exists, the description should provide more specifics on the return value.

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 input schema has two undocumented parameters (topic, project_path), and schema description coverage is 0%. The description barely adds meaning: topic is implied by 'version-accurate documentation' and project_path by 'this project,' but no explicit format or constraints are given.

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's purpose: 'Find the version-accurate Next.js documentation for THIS project.' It distinguishes from sibling tools by specifying it deals with documentation, not execution or indexing, and explicitly says it does not fetch docs.

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 provides explicit usage guidance: 'Call this before answering Next.js questions or writing Next.js code.' It also explains subsequent steps and upgrade handling. However, it does not explicitly exclude alternative tools or contrast with siblings.

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