list_next_data_fetching

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only enumerates topics (revalidate, generateStaticParams, etc.) and does not state what the tool actually does—whether it scans the project, returns code locations, or produces a report. No information is given about side effects, output format, or whether it is a read-only operation.

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 very concise, fitting in one line, and front-loads the core topic via a colon. It avoids unnecessary words, but it reads more like a fragment than a complete sentence and lacks an action verb, which slightly reduces 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?

Given the absence of an output schema and annotations, the description is incomplete for a tool that likely returns a list of data fetching constructs. It does not explain what results look like, how they are presented, or any prerequisites beyond the 'name' parameter. Sibling tools may hint at purpose, but the description itself is insufficient.

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 already provides a complete description for the single parameter 'name' (Name or path of the loaded project), achieving 100% schema description coverage. The tool description adds no additional parameter-level semantics, so the baseline score of 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 identifies the domain: data fetching, ISR, and cache in the Next.js app router, listing specific features. However, it lacks an explicit verb like 'List' or 'Find', leaving the action to be inferred from the tool name. It does distinguish from sibling tools by focusing on data fetching rather than routes or components.

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?

Usage is implied but not explicitly stated. The description suggests this tool is relevant when investigating data fetching patterns in Next.js, but it does not provide explicit guidance on when to use it versus alternative sibling tools like list_next_routes or list_next_api_routes. No exclusions or prerequisites are mentioned.

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