find_svelte_unused_stores

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

The description notes the heuristic nature of the analysis, which is a key behavioral caveat. However, it does not explicitly state that the tool is read-only, what side effects it has, or how results are returned. With no annotations, more disclosure would be beneficial.

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 sentence that front-loads the essential information about store types and the unused condition. No extraneous words.

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 definition is clear about the analysis criterion and heuristic nature, and the schema covers the parameter. It lacks an explicit statement of the return format, but the tool name and common sense for a 'find' tool imply a list of unused stores. For a simple one-parameter tool, this is adequate.

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 input schema fully documents the single 'name' parameter, and the description does not add further parameter-specific context beyond indicating the tool operates on a loaded project. The baseline of 3 applies given full 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 directly states what the tool does: it finds Svelte stores (writable/readable/derived) that are declared/exported but unused. This clearly distinguishes it from broader tools like find_unused_variables or find_dead_code by specifying store types and the heuristic limitation.

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 offers no explicit usage guidance, alternatives, or when-not-to-use. The intended use is implied by the name and coverage of 'template or script', but no comparison to sibling tools is provided.

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