hmc_list_password_policies

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

The readOnlyHint annotation already signals safety. The description adds behavioral detail by explaining what each policy_type value returns and specifying the per-policy dict structure ({UUID, title, link, ResourceType, Resource}), which goes beyond the annotation.

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 paragraphs: one sentence states purpose, the next explains the parameter and return format. No redundant text.

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?

Covers purpose, parameter behavior, and return shape for the default mode. The 'status' return is described only as 'activation status' without its structure, but since an output schema exists, this is a minor gap. Overall sufficient for a simple read-only list tool.

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 provides only an enum and default without descriptions (0% coverage). The description fully compensates by defining the two allowed values and their effects, plus the default choice and return structure.

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 opens with 'List HMC password policies,' a specific verb+resource statement. It further explains the policy_type parameter that selects between list and status modes, distinguishing it from other list 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 implies usage by naming the resource but does not explicitly state when to use this tool versus other list tools or alternatives like create/modify/delete password policies. No exclusionary guidance is provided.

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