nextjs_docs

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

No annotations provided, so description must cover behavior. It discloses the constraint that path must come from llms-index. However, it does not mention behavior on invalid path or return format. For a read-only fetch, this is adequate but could be more precise.

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?

Well-structured: purpose statement, important note, numbered workflow, example. Each sentence adds value; no superfluous text. Front-loaded with critical info.

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 simple tool, description covers usage workflow, parameter constraint, and provides example. Lacks details about output format but is sufficient for a documentation fetch tool.

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 covers 50% of params (path described, anchor not). Description adds value for path by reinforcing the need to get it from llms-index and giving an example, but does not address anchor at all. Compensates partially for missing schema coverage.

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 'Fetch Next.js official documentation by path', specifying verb (Fetch), resource (Next.js official documentation), and method (by path). It distinguishes from siblings like 'nextjs_index' and 'nextjs_call'.

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?

Provides explicit workflow: read llms-index resource, find path, then call tool. Includes emphasis ('MUST', 'Do NOT guess paths') and an example, leaving no ambiguity about prerequisites and correct usage.

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