DeleteLogGroup

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 behavioral disclosure. It says nothing about deletion being destructive or irreversible, required permissions, consequences for associated log streams, or any side effects.

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 is tautological and adds no value beyond the tool name. It is under-specified rather than concise, failing to 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 destructive delete operation with no annotations and no output schema, this description is critically incomplete. It leaves the agent guessing about the meaning of log_group_id, deletion scope, and preconditions, making confident invocation impossible.

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 schema covers 2 of 3 parameters with 'Overrides' descriptions, but the tool description itself adds no parameter meaning. The log_group_id parameter is left undocumented, and with moderate schema coverage (67%), the description should compensate but does not.

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 restates the tool name ('Huawei Cloud LTS operation DeleteLogGroup') without specifying that it deletes a log group. It is a tautology and provides no information that would distinguish it from sibling tools like DeleteLogStream or UpdateLogGroup.

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, what prerequisites exist, or how it relates to alternatives such as CreateLogGroup, UpdateLogGroup, or ListLogGroups. The description provides no usage context whatsoever.

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