Summarise the size and shape of a Signal Forms migration

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the behavior is largely covered structurally. The description reinforces the read-only guarantee and adds context about scanning behavior and result structure, but it does not disclose edge cases such as invalid paths or recursion behavior beyond what is already implied.

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 compact and front-loaded: the first sentence states the input and output details directly, and the second provides a clear read-only safety note. There is no fluff, redundancy, or unnecessary beat-around-the-bush phrasing.

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 has one required parameter, a simple input schema, output schema coverage, and clear annotations. The description supplies all the essential operational context: file types scanned, summarization outputs, file ordering rationale, and the mutation safety guarantee. Nothing critical 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 the single path parameter with 100% coverage. The description further clarifies that the tool scans .ts and .html files, and notes the directory alternative, adding practical meaning beyond the schema. There is slight ambiguity about whether a standalone .html file path is accepted, but overall the description usefully extends the schema.

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 uses a specific verb and resource: it scans .ts and .html files or a directory and summarises the migration. It also enumerates concrete outputs such as total findings, per-construct counts, and the mechanical/judgment split, which clearly distinguishes it from siblings like verify_migration or get_migration_report.

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 explains what the tool does and what it returns, but it does not explicitly state when to prefer this tool over siblings such as find_form_candidates or get_angular_upgrade_plan. It does not provide exclusions or an explicit when-to-use/when-not-to-use scenario, leaving usage mostly implicit.

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