migratorxpress_execute_command

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds valuable context: confirmation safety gate, prerequisite on preview, and failure condition (binary not installed). No contradictions.

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?

Two sentences, no unnecessary words. Front-loaded with core action and prerequisite. Every sentence provides essential information.

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?

Covers purpose, prerequisite, safety gate, and failure condition. Does not describe return values or success/error output, but output schema is absent. Annotations and schema are sufficient for basic usage.

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 100%, baseline 3. Description adds specifics: command must be copied from migratorxpress_preview_command output and is space-separated. Confirmation is explicitly linked to safety gate. Adds meaningful detail beyond 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?

Description clearly states the verb 'execute', the resource 'MigratorXpress command', and the prerequisite that the command must come from a prior preview call. It distinguishes itself from sibling tools like migratorxpress_preview_command by specifying it is for execution after building.

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 states when to use: after migratorxpress_preview_command, with confirmation=true. Mentions that the command must come from a prior call and that it will fail if binary is not installed. No explicit alternative comparisons, but context is clear.

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