release_version

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

The description discloses that the tool immediately makes the update available or starts a phased rollout, adding behavioral context beyond the annotations. Annotations already indicate destructiveness, and the description elaborates the effect, though it could mention reversibility or prerequisites.

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 sentences, front-loaded with the core action, and no wasted words. It efficiently conveys purpose, usage, and alternatives.

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's simplicity (2 required params, no output schema, annotations present), the description is complete. It covers purpose, state prerequisites, effects, and sibling alternatives adequately.

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?

With 100% schema coverage, the description adds no additional meaning beyond the schema's parameter descriptions. It meets the baseline for high coverage but does not enhance parameter understanding.

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 tool releases an approved App Store version from 'Pending Developer Release', specifying the verb and resource. It distinguishes itself from the sibling 'set_phased_release' by mentioning an alternative for gradual rollouts.

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?

It explicitly states when to use this tool (for versions in 'Pending Developer Release' state) and when not to use it (for gradual rollout, use set_phased_release instead), providing clear context and an alternative.

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