Find Angular Reactive Forms migration candidates

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

Despite readOnlyHint being true, the description goes well beyond that by explicitly stating the tool never modifies files, results are paged, the default page size, and what `incomplete` means. It also communicates the mechanical/judgment classification logic, which is valuable beyond the annotations. No contradiction with annotations.

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?

Three dense sentences each carry distinct value: scanning scope, read-only guarantee, paging, and filter guidance. The most important details are front-loaded and there is no filler.

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 tool is a read-only scanning utility, and the description covers all relevant operational aspects: input scope, safety, classification semantics, paging, and filtering. The presence of an output schema further covers return details, so no necessary information is missing.

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 documents all parameters at 100% coverage, so the baseline is high. The description adds value by framing constructs/classification as a 'work one decision at a time' workflow and by highlighting paging constraints in the overall behavior.

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 states the operation (scans .ts and .html files or a directory), the object (Angular Reactive Forms constructs), and the output distinction (mechanical vs. judgment). This differentiates it from sibling tools like analyze_migration_complexity or get_migration_report, which focus on broader analysis or reporting.

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?

It explicitly describes path-based scanning, result filtering, and pagination workflow, saying to check `incomplete` for more results. It does not explicitly say when NOT to use this tool in favor of a sibling, but the operational guidance for how to use this tool is clear.

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