list_nuxt_page_meta

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The description conveys that the tool extracts per-page definePageMeta with specific fields, but it does not state whether pages without meta are included, the output format, or that it is a read-only operation. The 'list' action implies non-mutating behavior, but this is not explicitly disclosed.

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 compact, information-dense fragment that lists the relevant metadata fields without wasted words. It is appropriately sized for a simple list tool, though it could be structured as a full sentence to improve formality.

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 single parameter, no output schema, and no annotations, the description covers the core purpose and key fields. However, it omits practical details such as whether the tool returns all pages or only those with definePageMeta, and what the output structure looks like. These gaps limit completeness for a tool that is otherwise straightforward.

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 provides 100% coverage for the single parameter 'name' with a clear description, so the baseline is 3. The tool description adds no additional parameter meaning beyond what the schema already states, and does not reference the parameter at all.

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 indicates that the tool involves definePageMeta per page and enumerates the specific fields (layout, middleware, title, validate, pageTransition, name). It is distinct from sibling tools like list_nuxt_pages, which focus on page discovery. However, it lacks an explicit verb such as 'list' or 'display', relying on the tool name to convey 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?

Usage is implied by the Nuxt-specific scope and the enumerated meta fields, which separates it from other Nuxt analysis tools. However, there is no explicit guidance on when to use this tool over alternatives like list_nuxt_pages or analyze_vue_component, nor are there exclusions or prerequisites mentioned.

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