hcloud_list_vpn_ike_policies

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no mention of whether results are region-scoped, whether the list is paginated or truncated, or what a policy object contains — all things annotations cannot convey.

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 a single four-word phrase with zero redundancy and is trivially front-loaded, but this is brevity by omission rather than economy of expression. Nothing is wasted because almost nothing is said.

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?

With no output schema and a crowded sibling set containing a near-identical IPsec policy tool, the description should at minimum clarify scope and disambiguation. It provides neither, leaving the agent unable to tell what this returns or why it differs from adjacent VPN list tools.

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 description coverage is 100%, so the single required parameter 'region' is documented in the schema, and per the high-coverage baseline a 3 applies. The description adds no extra meaning such as accepted region formats or whether region changes the result set.

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 phrase 'List VPN IKE policies' does name a verb and a resource, so the basic operation is identifiable. However, it is essentially a restatement of the tool name with no scope detail, and it does nothing to distinguish this tool from the very similar sibling hcloud_list_vpn_ipsec_policies, which an agent could easily confuse with it.

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 when-to-use guidance at all: no statement of what the policies are for, no prerequisite (e.g. a VPN gateway must exist), and no explicit routing to or away from hcloud_list_vpn_ipsec_policies, hcloud_list_vpn_connections, or hcloud_show_vpn_gateway. The agent must infer selection from the name alone.

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