nextjs_code_review

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

The description indicates it analyzes code and returns results, but lacks details on behavioral traits such as being read-only, required permissions, or potential side effects. With no annotations provided, the description should carry the burden of transparency but falls short.

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 concise with two sentences, front-loading the purpose. No unnecessary words, and it is well-structured for quick understanding.

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 is adequate for a simple analysis tool, but lacks details about the output format and does not fully leverage the context of having many sibling tools. It could benefit from specifying that results are returned in a structured format.

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%, so the parameter descriptions are adequate. The tool description adds context about the analysis dimensions but does not enhance understanding of parameter usage beyond the schema.

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 analyzes React/Next.js code for SEO, performance, and accessibility, and returns issues and suggestions. It distinguishes itself from sibling tools like check_accessibility and get_seo_recommendations by performing a combined review.

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 implies the tool is for a general code review covering multiple aspects, but it does not explicitly state when to use this tool versus more specific sibling tools. No guidance on prerequisites or context.

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