list_nuxt_pages

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

With no annotations, the description must disclose behavior, but it only describes the data sources. It does not explicitly state this is a read-only listing, any prerequisites, side effects, or return format. The parameter description hints at a loaded project, but that is from the schema, not the tool description.

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 a single concise clause with no redundant words. It efficiently packs the route sources and dynamic/catch-all details into one line, though it could be slightly more explicit with a verb.

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?

This is a simple tool with one parameter, but without an output schema, the description should clarify the return value or any behavioral preconditions. It explains what routes are covered but not the output format or that it requires a loaded project (only implied by the schema).

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 clear description for the name parameter (100% coverage), and the tool description adds no additional parameter meaning. Baseline 3 is appropriate since the schema handles the documentation.

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 resource scope: routes from pages/ and server/api, including dynamic params and catch-all. It distinguishes from siblings like list_nuxt_server_api by combining both sources, but lacks an explicit verb in the description itself, relying on the tool name for the action.

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 usage when you need routes from both pages and server/api, but it does not explicitly state when to use this tool versus alternatives like list_nuxt_server_api or list_nuxt_page_meta, nor any exclusions.

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