ShowNotificationTemplate

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

No annotations are provided, so the description carries full burden. It discloses no behavioral traits such as read-only nature, return format, pagination, or error behavior. The word 'Show' implies retrieval, but the description itself adds nothing.

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 short but tautological and under-specified. It does not earn its place as it provides no useful information beyond the tool name.

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 4-parameter operation with no annotations, no output schema, and no usage context, this description is completely inadequate. The agent cannot determine what this tool does, how to invoke it properly, or what to expect in the response.

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?

Schema description coverage is 50% (region and project_id have descriptions, domain_id and template_name do not). The tool description adds no additional parameter meaning beyond the schema, failing to clarify the role of template_name or other parameters.

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 ShowNotificationTemplate.' merely restates the tool name and offers no verb or resource clarification. It fails to distinguish this from sibling tools like ListNotificationTemplate or CreateNotificationTemplate.

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. It does not explain whether to use Show vs List, or mention any prerequisites or context for retrieving a notification template.

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