Migrate Base Plan Prices

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

No annotations are provided, so the description must carry the behavioral burden. It adds one useful operational trait: 'Disabled in read-only mode.' However, it does not disclose whether the migration is destructive, irreversible, or how it affects existing subscribers, which is significant for a mutation tool.

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 two short sentences with no filler. The primary purpose is front-loaded and the operational constraint is concise.

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 full schema coverage and presence of an output schema reduce the need for parameter and return-value explanation. Still, for a subscriber-migrating mutation with no annotations, the description lacks context about migration scope, irreversibility, and when to choose this over batch_migrate_base_plan_prices.

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 input schema provides descriptions for all 4 parameters, including useful examples for the request body. The description itself adds no additional parameter-level meaning, so the baseline of 3 applies.

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 states a specific action and resource: 'Migrate subscribers to the current base plan prices.' This clearly identifies what the tool does. However, it does not explicitly differentiate this from the sibling batch_migrate_base_plan_prices, relying on the tool name to carry that distinction.

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?

There is no guidance about when to use this tool versus alternatives like batch_migrate_base_plan_prices or convert_region_prices. The note 'Disabled in read-only mode' is an operational constraint, not guidance about selecting this tool over siblings.

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