subscription_base_plans_migrate_prices

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

No annotations provided, so the description must fully disclose behavioral traits. It only states 'apply a price change' but does not mention effects on subscriptions, reversibility, permissions, or response behavior. Minimal transparency beyond the basic action.

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 a single sentence that efficiently conveys the primary action. It is front-loaded but lacks structure. While concise, it omits important detail; however, it is not verbose.

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?

For a complex price migration operation with no output schema and low schema coverage, the description is insufficient. It does not explain the migration process, constraints, or expected outcomes, leaving the agent with inadequate context to invoke the tool correctly.

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 only 33%. The description adds no explanation for parameters like basePlanId, regionalPriceMigrations, regionsVersion, or latencyTolerance. It does not compensate for the low coverage, leaving critical parameters underdocumented.

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 verb 'apply a price change', the resource 'existing subscribers of a base plan', and the scope 'specific regions'. It distinguishes this tool from siblings like subscription_base_plans_activate and subscription_base_plans_batch_migrate_prices.

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?

No guidance on when to use this tool versus alternatives such as subscription_base_plans_batch_migrate_prices. The description lacks when-to-use, when-not, or contextual prerequisites.

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