blueprint_un_release_blueprint_version

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond restating the HTTP path — it does not say what 'unrelease' actually does to catalog availability, whether running deployments are affected, or whether authorization beyond normal is needed.

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 short, front-loaded lines with the action stated first. The raw POST path duplicates the annotation title, so it is slightly redundant, but nothing is bloated.

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 state-changing catalog operation with no output schema, the description omits the important consequences: what happens to catalog items or deployments referencing that version, and whether the operation is reversible. An agent can guess the intent but not the impact.

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 coverage is 100%, so blueprintId and version are already documented. The description only echoes the path template and adds no meaning about format, required state, or what apiVersion changes. Baseline 3 applies when the schema carries the load.

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 specific verb+resource pair: 'UnRelease versioned blueprint from catalog', which is clearly distinct from the sibling blueprint_release_blueprint_version and blueprint_restore_blueprint_version. It stops short of explicitly naming those siblings or explaining the difference between unrelease and restore.

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 choose unrelease over release/restore/delete, and no prerequisites are stated (e.g., that the version must currently be released). The usage has to be inferred entirely from the verb.

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