hcloud_list_cfw_service_rules

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not mention pagination behavior, that region scoping is mandatory, or how results relate to object_id, which would be valuable context for a list operation.

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?

A single short phrase, front-loaded with the verb and resource, with no wasted wording. It is terse to the point of under-specification, but nothing in it is extraneous.

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 four parameters, a required region, and no output schema, the description should at minimum explain what a service rule contains and how pagination returns results. Instead it provides only the tool's name restated in prose, leaving the agent to rely wholly on structured fields.

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 all four parameters (limit, offset, region, object_id) are already documented in the schema, establishing a baseline of 3. The description adds no additional meaning beyond the schema, such as what a protection object is or whether filters combine.

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 a specific verb ("List") and a specific resource ("CFW (Cloud Firewall) service rules"), and expands the CFW acronym so the agent knows the domain. It implicitly distinguishes itself from siblings like hcloud_list_cfw_firewalls and hcloud_list_cfw_acl_rules by naming a different rule collection, though it never explicitly contrasts them.

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 use this tool versus alternatives such as hcloud_list_cfw_acl_rules or hcloud_list_cfw_firewalls, and no stated prerequisites or exclusions. The agent must infer usage entirely from the tool name.

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