find_svelte_effect_leaks

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the analysis is heuristic and lists the specific patterns checked (addEventListener, setInterval, subscribe), which is useful. However, it does not indicate read-only nature, output format, or potential false positives beyond the word 'heuristic'.

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, compact clause that front-loads the key pattern (onMount) and specifies the resource types. Every word contributes meaning, with no wasted text. It could be considered under-specified but is still concise and clear.

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?

With no output schema, the description would ideally explain what the tool returns (e.g., list of affected components/locations), but it does not. It also doesn't mention scope or limitations beyond 'heuristic'. The core detection logic is described, which is sufficient for a simple find tool, but additional context would improve completeness.

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 single parameter 'name' is fully documented in the schema as 'Name or path of the loaded project', providing 100% coverage. The description adds no additional parameter semantics beyond what the schema already specifies. Baseline score of 3 is appropriate.

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 identifies the tool as a Svelte-specific static analysis that detects onMount callbacks registering listeners/timers/subscriptions without cleanup in onDestroy. This is specific and distinguishes it from sibling tools like find_react_effect_leaks or find_event_listener_leaks. However, it is phrased as a noun phrase rather than a full sentence, which slightly reduces clarity.

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 guidance on when to use this tool versus alternatives like find_react_effect_leaks or find_event_listener_leaks. The Svelte-specific pattern and the term 'heuristic' imply usage context but do not state it directly. There are no exclusions or alternative references.

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