batch_migrate_base_plan_prices

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool is disabled in read-only mode (implying a write operation) but provides no details on side effects, reversibility, authentication requirements, or rate limits. The phrase 'migrate prices' is vague and does not clearly indicate whether it overwrites, appends, or transforms data.

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 extremely concise—two sentences, no redundancy, and front-loaded with the core purpose. Every phrase earns its place, and it wastes no words on fluff or repetition.

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 description provides a basic understanding of the batch operation and its read-only restriction, and an output schema exists to define return values. However, it does not explain what 'migrate prices' entails (e.g., whether it updates, overwrites, or transfers prices), nor does it mention any prerequisites or dependencies. For a batch write operation, more context would be helpful, but the existing information is just adequate.

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 description coverage is 100% for all three parameters, so the schema already documents each parameter. The description adds no additional semantic meaning to the parameters; it only mentions the operation itself. Baseline 3 is appropriate given that the schema does the heavy lifting.

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 action (migrate prices) and the scope (multiple base plans in a single operation). It explicitly differentiates from the singular 'migrate_base_plan_prices' sibling by emphasizing batch processing, making the purpose unambiguous.

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?

The description notes that it is disabled in read-only mode, providing a clear condition for when not to use it. It also implies a batch use case by mentioning 'multiple base plans' and 'single operation,' which guides the agent toward this tool for bulk migrations. However, it does not explicitly mention alternatives or when to prefer the singular version, leaving slight room for improvement.

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