ListCriterias

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It gives no information about side effects, required permissions, pagination, return format, or any other behavioral traits. The description is entirely 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 description is extremely brief, but this is under-specification rather than conciseness. It is a single phrase that merely names the operation, providing no useful structure or substance.

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 tool's complexity (5 parameters, no output schema, no annotations) and the large set of sibling tools, the description is woefully incomplete. It does not explain what the tool returns, how it differs from similar list tools, or any operational details, making it nearly impossible for an agent to select and invoke correctly.

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 adds no meaning to the parameters. While the schema covers 40% of parameters (region and project_id have descriptions), the remaining 60% (group_id, topic_id, search_type) are undocumented, and the description does not compensate. With low schema coverage, the description should clarify the parameters but does not.

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 ListCriterias' restates the tool name without specifying what it does. It lacks a clear verb and resource, and does nothing to distinguish this tool from siblings like ListQueryAllSearchCriterias or CreateSearchCriterias.

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 or when to use an alternative. The description provides zero context about the intended use case, prerequisites, or relationship to sibling tools.

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