DeleteConsumerGroup

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

With no annotations, the description carries the full burden of disclosing behavioral traits such as side effects, permissions, or reversibility. It discloses nothing beyond the operation name, leaving the agent completely uninformed about what executing this tool does in practice.

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 sentence, but brevity here results from under-specification rather than efficient structure. It contains no useful content beyond the title, making it too sparse to earn a passing score for conciseness.

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 5 parameters, no annotations, and no output schema, this description is wholly inadequate. It provides no context about the operation's purpose, effects, or return values, leaving the agent without enough information to invoke it 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 coverage is only 40%, and the description provides no parameter information at all. The meaningful parameter names like consumer_group_name, group_id, and stream_id are left unexplained, and the description does not compensate for the schema's gaps.

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 DeleteConsumerGroup" only restates the tool name with the vague term 'operation' and provides no actual verb or resource detail. It doesn't explain that this tool deletes a consumer group, which is inferable from the name but not stated. It also fails to distinguish itself from sibling tools like CreateConsumerGroup or ListConsumerGroup.

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?

No guidance is given about when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. The description is purely nominal and offers no situational cues.

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