list_sveltekit_routes

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

With no annotations, the description carries the transparency burden. It discloses the directory convention and the file types considered routes, which is useful. However, it does not state what the tool returns (e.g., route paths, file paths), whether it scans recursively, or any read-only guarantees, leaving uncertainty about its output behavior.

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, dense sentence that front-loads the core purpose and lists the relevant file types. Every element is informative, with no filler or redundancy.

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 lack of an output schema, the description should clarify the return format and coverage scope, but it does not. It mentions the key file types but omits details like dynamic segments, route groups, or whether the listing includes all levels of nesting. This is not fully complete for an unannotated list 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?

The schema already provides a full description of the 'name' parameter ('Name or path of the loaded project'), and the tool description adds nothing about parameters. With 100% schema coverage, the baseline of 3 applies.

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 tool as listing SvelteKit routes based on the src/routes directory convention, enumerating the specific file types included. It distinguishes this from sibling tools like list_sveltekit_load_actions or list_nuxt_pages by focusing on SvelteKit route files.

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 provides no explicit when-to-use guidance or mention of alternatives. It implies usage for SvelteKit projects, but there is no comparison to other route-listing tools or exclusions, leaving the agent without clear selection criteria beyond the name.

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