ListHistorySql

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

No annotations are provided, so the description must fully disclose behavior. It does not mention any side effects, permissions, pagination, return format, or other behavioral traits. The description is entirely empty of behavioral information.

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 a single, uninformative phrase. This is under-specification, not conciseness. It offers no structured information about purpose, usage, or behavior.

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 no annotations, no output schema, and minimal parameter guidance, the description is wholly inadequate. The tool is one of many similar list operations, and without additional context, even the basic purpose is unclear.

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%, with log_group_id and log_stream_id having no descriptions. The tool description adds no parameter meaning whatsoever, failing to compensate for the missing schema details. Even the described parameters (region, project_id) are self-explanatory, but their relationship to the operation is not clarified.

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 'Huawei Cloud LTS operation ListHistorySql.' which is a tautology—it restates the name without providing any verb, resource, or outcome. It does not explain what ListHistorySql does, making it impossible to distinguish from the many other List* sibling tools.

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 versus alternatives. With over 70 sibling tools, many of which are also list operations, the lack of any context or exclusions leaves the agent without direction.

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