CreateAomMappingRules

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

No annotations are provided, so the description carries the full burden for behavioral disclosure, but it discloses nothing—no mention of side effects, permissions, whether it's a write operation, or return behavior. The name hints at creation, but the description itself is devoid of 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 short but under-specified, not concise. The single sentence merely rephrases the title with generic words ('Huawei Cloud LTS operation') and provides no substantive content, so it fails to earn its place as useful documentation.

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 complex nested body schema, four parameters, and a large family of sibling tools, the description is severely incomplete. There is no output schema to compensate, and the tool description provides no information needed for correct invocation, especially considering AOM mapping rules are a niche Huawei Cloud concept.

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 description does not mention or explain any of the four parameters (body, region, is_batch, project_id) or the nested structure of body. With 50% schema description coverage, the tool description adds zero semantic value, leaving the agent to infer everything from parameter names alone.

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 is essentially a tautology: 'Huawei Cloud LTS operation CreateAomMappingRules' restates the tool title without providing a verb or resource. It does not clarify what creating AOM mapping rules actually entails or distinguish it from sibling tools like UpdateAomMappingRules or ShowAomMappingRules.

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. The description is silent on context, prerequisites, exclusions, or relationships to other tools, offering no actionable direction for an agent.

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