DeleteAomMappingRules

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. However, it says nothing about the destructive nature of the operation, whether the deletion is permanent, requires special permissions, or has any side effects. The tool name implies deletion, but the description itself offers zero behavioral context.

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 very short, but this is under-specification rather than concise clarity. It contains no useful information beyond the tool name, so while there is no verbosity, the single sentence fails to communicate anything substantive.

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 delete operation with no annotations and no output schema, the description should state the affected resource, required identifiers, and likely consequences. It provides none of this, leaving the agent with insufficient context to safely invoke the tool.

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 documentation covers 67% of parameters (region and project_id as overrides), but the 'id' parameter is undocumented. The description does not clarify what 'id' refers to (e.g., the mapping rule ID), nor does it explain how the parameters relate to the deletion. The description adds no semantic value beyond the schema.

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 states 'Huawei Cloud LTS operation DeleteAomMappingRules,' which essentially restates the tool name without explaining what the operation does. It uses the tool name as both subject and action, making it a tautology rather than a clear purpose statement.

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 compared to siblings like CreateAomMappingRules, UpdateAomMappingRules, or ShowAomMappingRules. It does not state that this is the deletion tool for AOM mapping rules or mention any prerequisites.

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