hmc_delete_media_repository

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

Annotations indicate destructiveHint=true, and the description adds valuable context by stating this is an immediate synchronous delete with no job to poll, returning a confirmation string. This goes beyond the annotation's safety warning to clarify execution mode.

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 three sentences with zero fluff, front-loading the purpose before explaining the parameter format and synchronous behavior. Every sentence contributes.

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 two-parameter delete operation, the description covers the purpose, the synchronous nature, and the vios identifier format. The output schema presumably documents the return confirmation string, so the description is complete enough. It could explicitly clarify vg_uuid, but the tool name and purpose make it predictable.

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 input schema provides no descriptions (0% coverage). The description explains vios_name_or_uuid as accepting either a PartitionName or a UUID (findable via hmc_vios), which adds meaning. However, vg_uuid is not explained, though its role is implied by the tool's purpose.

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 'Delete the Virtual Media Repository from a Volume Group,' which is a specific verb+resource+target. This distinguishes it from sibling tools like hmc_create_media_repository and other delete operations.

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 does not explicitly state when to use this tool versus alternatives, but it implies usage by identifying the resource to delete and instructing 'find it with hmc_vios' for the vios_name_or_uuid parameter. No exclusions or alternative tool references are provided.

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