ListNotificationTemplate

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

No annotations are provided, so the description must disclose behavioral traits such as read-only vs. write, pagination, filtering, permissions, or response shape. It does none of this, leaving the agent with zero understanding of side effects or operational behavior.

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 this is under-specification, not conciseness. The single sentence contains no operational information and does not front-load any useful content for tool selection or invocation.

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?

With 4 parameters (one nested with 3 fields), no output schema, no annotations, and a large set of sibling tools, the description is grossly incomplete. It fails to explain the request/response shape or the tool's place in the Huawei Cloud LTS API.

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 includes generic override descriptions for region and project_id, but the tool description adds no parameter meaning. The body object's source, language, and templates fields are opaque, and with only 50% schema coverage the description should compensate but fails to do so.

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 a tautology: 'Huawei Cloud LTS operation ListNotificationTemplate' restates the tool name and only adds the vendor/service context. It lacks a specific verb (e.g., list/get), does not describe what the tool returns, and cannot be distinguished from the sibling ListNotificationTemplates.

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 instead of alternatives like ListNotificationTemplates or ShowNotificationTemplate. No context, prerequisites, or exclusions are provided.

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