ListConsumerGroup

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

No annotations are provided, so the description carries the full burden of explaining behavior. It discloses no side effects, permissions, read-only nature, or other traits. The description adds nothing beyond the tool name.

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?

Although the description is very short, it is under-specified rather than concise. The single sentence merely restates the tool name and adds no useful content, so it does not earn its place.

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 with 4 parameters, no output schema, no annotations, and a closely related sibling ListDetailsConsumerGroup, this description is grossly incomplete. It does not explain what the operation does, what parameters mean, or how it differs from alternatives.

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 input schema describes region and project_id, but group_id and stream_id are completely undocumented. With 50% schema coverage and no parameter explanation in the description, the agent cannot infer the meaning or required format of these key parameters.

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 only repeats the operation name ('Huawei Cloud LTS operation ListConsumerGroup') without stating what it lists or what a consumer group is. It is a tautology that does not distinguish itself from sibling ListDetailsConsumerGroup or other list operations.

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 ListDetailsConsumerGroup, DeleteConsumerGroup, or CreateConsumerGroup. No context, prerequisites, or exclusions are provided.

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