analyze_migration_for_testing

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

With no annotations, the description fully discloses behavior: it inspects and analyzes, returns risk scoring and recommendations. No mention of modification or destruction, consistent with a read-only analysis tool. It details what is checked and the output format.

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 concise with bullet points for inspections and a summary sentence. It is front-loaded with the main purpose and each sentence contributes value. No redundant or unnecessary text.

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 7 parameters and no output schema, the description covers the tool's purpose, inputs, inspections, and outputs (risk scores, test recommendations). It also provides a usage ordering hint. It could be more complete by specifying the output structure, but the description suffices for an agent to decide to invoke it.

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?

Schema coverage is 71% (5 of 7 parameters have descriptions). The description adds context by linking inspections to parameters (e.g., staging table accessibility to staging_table). It also clarifies the purpose of sample_records for null-rate analysis. However, field_mappings and transform_rules have no schema descriptions and the description doesn't elaborate on them.

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 tool analyzes a migration setup to identify risks and plan test coverage, listing specific inspections. It distinguishes from sibling tools like analyze_dependencies and create_migration_test_plan, providing a specific verb and resource.

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?

Explicitly says 'Always call this FIRST before create_migration_test_plan', providing clear sequential guidance. Implies usage context and alternatives (the sibling create_migration_test_plan serves as the next step).

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