CreateNotificationTemplate

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 disclosing behavior. It states nothing about side effects, required permissions, rate limits, or what the operation does to resources. The description is completely uninformative.

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 single sentence is very short but not concisely informative—it is an under-specification that does not earn its place. It provides no value beyond the tool name itself.

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?

Although the schema shows nested objects, there is no operational context, no return value description, and no behavioral details. For a tool with this complexity and no output schema, the description is severely inadequate.

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 has 4 parameters including a nested body object, but the description adds zero explanation about parameter meanings or relationships. With only 50% schema coverage and no description support, the agent has no assistance in constructing a valid request.

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 CreateNotificationTemplate' is a tautology—it merely restates the tool name with generic wording. It provides no specific verb, resource, or action detail, so the agent cannot determine what the tool actually does.

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. Sibling tools like UpdateNotificationTemplate and ListNotificationTemplate exist, but the description gives no context for selecting among them.

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