hcloud_list_bss_measurements

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds only the acronym expansion and does not explain what a BSS measurement represents, what is returned, or any pagination behavior beyond the schema.

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 front-loaded sentence with no wasted words. It is appropriately sized for a simple list tool, though it is so terse that it omits helpful routing context.

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 tool that must be distinguished from many sibling list/show tools, the description is incomplete: it does not clarify what BSS measurements are or how they relate to customer orders and account balance. The annotations reduce the behavioral burden, but the agent still lacks enough context to confidently select this tool over siblings.

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% for the two pagination parameters, so the schema already defines limit and offset clearly. The description does not add any meaning beyond the schema, which meets the baseline of 3 when the schema carries parameter semantics.

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 resource (BSS measurements), and expands the acronym to Billing and Subscription, which helps an agent understand the domain. It does not distinguish this tool from sibling BSS tools such as hcloud_list_bss_customer_orders or hcloud_show_bss_account_balance.

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 explicit guidance on when to use this tool versus the other BSS siblings. The usage is only implied by the tool name; no exclusions or alternative conditions are provided.

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