hcloud_list_lts_groupsRetrieve LTS log groups for a specified region with pagination support, enabling AI assistants to inspect Huawei Cloud log resources.
List LTS (Log Tank Service) log groups
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results | |
| offset | No | Pagination offset | |
| region | Yes | Region |
Changes observed during successful MCP inspections.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered by structured data. The description adds only the acronym expansion and says nothing about pagination behavior, result caps, or the fact that the call is region-scoped. With annotations carrying the behavioral load, this is adequate but thin.
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 front-loaded sentence with no filler; the parenthetical acronym expansion is the one addition and it earns its place. It is efficient, though bordering on under-specified rather than maximally informative.
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 simple read-only list tool with full schema coverage and no output schema, the definition is just barely sufficient. The missing pieces are how this collection relates to LTS streams and what the region parameter means for reachability, which an agent would need to chain calls correctly.
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, offset and region all documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema — not even which region values are valid or how limit/offset interact.
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?
States a specific verb ('List') and resource ('LTS log groups') and expands the LTS acronym, so the agent knows exactly what entity is returned. It does not explicitly distinguish this from the sibling hcloud_list_lts_streams, leaving the groups-vs-streams boundary implicit.
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 of when to prefer streams or another sibling, and no statement of prerequisites. The only hint that a region is mandatory comes from the schema's required list, not the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.