ListHostGroup

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It provides none: no read-only/write indication, no mention of pagination, return format, or required permissions. The agent cannot anticipate side effects or response structure.

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?

One sentence is concise in length, but it is under-specification, not efficiency. It contains no substantive information beyond the tool name, so it fails to earn its place as a meaningful description.

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 has nested parameters, no output schema, and no annotation context. The one-line description leaves the agent without essential information about filtering options or list behavior, making it completely inadequate for a tool of this complexity.

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?

The description adds no parameter semantics. While region and project_id have schema descriptions ('Overrides HUAWEI_REGION.'), the body/filter object is entirely undocumented in both schema and description. With 67% schema coverage, the main parameter lacks any meaning beyond its name.

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 'Huawei Cloud LTS operation ListHostGroup' merely restates the tool name and prefixes the service name. It does not state what the operation does (e.g., listing host groups with optional filters) or distinguish it from sibling tools like ListHost. This is a tautology.

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 ListHostGroup versus ListHost or other list operations. No use cases, exclusions, or alternatives are mentioned.

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