ShowAomMappingRules

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions no behavior at all—whether the operation is a read-only list, what it returns, or if any side effects occur. It adds zero value beyond the 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?

The description is short but not meaningfully concise—it wastes the only sentence on a restatement of the name. Under-specification is not conciseness; the sentence 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?

Given the absence of annotations, no output schema, and a sibling tool with a similar name, the description is wholly inadequate. It fails to explain what the operation does, what it returns, or how it relates to other mapping rule tools, leaving an agent with no basis for correct selection or invocation.

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 provides complete descriptions for both parameters ('Overrides HUAWEI_REGION' and 'Overrides HUAWEI_PROJECT_ID'), yielding 100% coverage. The tool description adds no additional parameter context, so the baseline of 3 applies.

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 ShowAomMappingRules' is a tautology—it simply restates the tool name with a service qualifier. It does not explain what AOM mapping rules are, what 'Show' does (list vs. get), or how it differs from sibling ShowAomMappingRule.

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 alternatives like CreateAomMappingRules or ShowAomMappingRule. The description lacks any contextual cues about use cases, prerequisites, or distinctions.

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