ListTopnTrafficStatistics

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

No annotations are present, and the description provides no behavioral details such as what data is queried, whether it is read-only, pagination behavior, rate limits, or prerequisites. The description carries the full burden and fails completely.

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 short but this is under-specification, not conciseness. It lacks any meaningful content, making it unhelpful despite its brevity.

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?

This is a complex tool with nested objects, no output schema, and no annotations. The description is a single sentence that adds no value, leaving the agent without essential context for invocation. It is completely 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 moderate 67% coverage (region and project_id have descriptions), but the 'body' parameter and all nested properties are undocumented. The description adds no parameter meaning whatsoever, leaving users to guess the semantics of fields like 'topn', 'filter', and 'sort_by'.

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 ListTopnTrafficStatistics' is a tautology that merely restates the tool name. It does not specify what the tool does, what resource it acts on, or what 'ListTopnTrafficStatistics' means, making purpose entirely unclear.

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?

No guidance is provided on when to use this tool or how it differs from alternatives. Notably, sibling tool 'ListTimeLineTrafficStatistics' appears similarly named, but no distinction or selection criteria are offered.

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