add_isolated_release_choice

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description adds real value by noting that the hash must be a *reviewed* exact hash and that dependencies require review (mapping to acknowledge_dependencies), but it stays silent on acknowledge_unprotected_write, which is a meaningful gate for a destructive write.

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?

A single front-loaded sentence with no filler; the preview-vs-write distinction comes first. It is efficient, though the brevity is partly the cause of the coverage gaps rather than a virtue in itself.

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 destructive, non-idempotent tool with 14 parameters, 9 required, no output schema and almost no schema descriptions, one sentence is not enough. The agent knows the hash and dependency-review requirement but not what the call actually mutates, what the profiles represent, or what acknowledgement flags must be set.

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 14 parameters, 9 required, and only 14% schema description coverage, the description carries most of the burden and does not meet it. It gestures at isolated_definition_hash and the dependency acknowledgment flags, but leaves current_members, isolated_choice_id, logical_name, attribute_name, solution_unique_name, dry_run and acknowledge_unprotected_write entirely unexplained.

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 gives a verb ("Preview or add") and a resource ("reviewed isolated component"), and the preview mode is discernible. However, it never says the resource is a *choice*, so the agent cannot easily tell it apart from add_isolated_release_field or add_isolated_release_webresource, which share the identical phrasing pattern. The purpose is inferable but not sharp.

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?

"source differences and dependencies require review" implies preconditions but names no alternative tool and gives no explicit when-to-use rule. Nothing tells the agent to call stage_isolated_choice_candidate or review_release_dependencies first, or publish_isolated_release_component afterwards, so sequencing must be guessed from sibling names.

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