hcloud_list_smn_subscriptions

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 note on pagination via limit, no statement about result ordering or what happens when topic_urn is omitted.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. However, that brevity comes from under-specification rather than disciplined editing, so it does not earn full marks.

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?

The tool is simple (three flat parameters, one required, no output schema), but the description still leaves the SMN subscription model and the topic relationship unexplained. Given an abbreviation-heavy name and dozens of sibling list tools, it should do more to orient the caller.

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%, with limit, region and topic_urn each carrying inline text, so the baseline of 3 applies. The description contributes no additional meaning such as whether limit is a page size or a hard cap.

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?

"List SMN subscriptions" restates the tool name with the vendor prefix removed and adds no distinguishing information. It does identify a verb and a resource, but 'SMN subscriptions' is never expanded or explained, and nothing separates it from sibling listing tools such as hcloud_list_smn_topics.

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, no mention that subscriptions belong to a topic and can therefore be filtered via topic_urn, and no reference to any sibling tool. An agent must infer the workflow entirely from the parameter names.

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