app_store_version_phased_releases__create

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

Given existing annotations (readOnlyHint=false, destructiveHint=true), the description adds useful context: the rollout spans 7 days, targets approved versions, and is a write operation. It doesn't contradict annotations, though it doesn't elaborate on the destructive implications.

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 concise sentences convey the purpose, duration, prerequisite, HTTP method, and operation level. No wasted words.

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 simple create operation with no output schema, the description adequately explains the action, duration, and prerequisite. The nested body schema handles the structural details; the description adds the high-level purpose and conditions.

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 schema covers 100% of the parameters (body), and the description adds no parameter-specific guidance. The baseline of 3 applies because the schema itself provides the necessary structure.

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 a specific action (Start a phased rollout), the target resource (approved version), and the key behavior (gradual percentage increase over 7 days). It also includes the HTTP endpoint, distinguishing it from related operations like update or delete.

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?

Provides a clear prerequisite ('approved version') and implies when to use it (to begin a rollout). It doesn't explicitly mention alternatives like update or delete, but the context of a create operation is evident from the name and description.

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