hmc_delete_password_policy

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

Beyond the destructiveHint annotation, the description discloses permanence ('irreversible'), return format ('confirmation string'), and execution model ('immediate delete — no job to poll'). No contradiction with annotations.

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?

Three sentences, each earning its place: the action, the risk/reversibility, and the return/behavior. Front-loaded with the primary purpose; no filler.

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 deletion tool with one parameter, destructive annotation, and an output schema, the description covers the essential context: what it does, how to prepare, what to expect in response, and why confirmation is needed. Nothing important is missing.

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 has one self-explanatory parameter (policy_name), but schema coverage is 0%. The description clarifies that the parameter should be verified against the list of policies, adding meaning beyond the schema. It doesn't specify exact name format, but the name is clear enough.

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 states the specific action ('Delete an HMC password policy'), the resource ('password policy'), and the identifying attribute ('by name'). It clearly distinguishes from sibling tools like create/modify/list password policy.

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 explicit pre-call guidance: 'Confirm the policy_name with hmc_list_password_policies before calling.' Also notes the operation is immediate (no job to poll), setting expectations for usage.

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