migrate_base_plan_prices

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

With no annotations provided, the description must disclose behavioral traits fully. It only mentions 'Disabled in read-only mode,' which is a constraint, but omits side effects on subscriber data, whether the operation is reversible, or any other impacts. This is insufficient for a migration tool that likely changes prices.

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 sentences, front-loaded with the main purpose and a caveat. Every word is useful, and it is appropriately sized.

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 the tool has a nested request object and an output schema, the description covers the basics but lacks detail about the request structure or implications of migration. For a potentially impactful operation, more context would be beneficial, but it is adequate for a simple tool with well-documented schema.

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 has 100% coverage with descriptions for all four parameters, so the baseline is 3. The description adds no extra parameter context, but it doesn't need to given the schema's completeness.

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 it migrates subscribers to current base plan prices, using a specific verb and resource. However, it does not differentiate from the sibling batch_migrate_base_plan_prices, which is a similar operation, so it loses a point for lacking 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 on when to use this tool versus alternatives like batch_migrate_base_plan_prices, no prerequisites, and no scenarios are mentioned. The description only states what it does, not when or why to choose it.

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