ListCharts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals nothing about pagination, required vs optional parameters, return behavior, permissions, or side effects. The description simply restates the operation name.

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 sentence, but it is under-specified rather than concise. It contains zero informative content beyond what the name already conveys, making it a tautological label rather than a useful summary.

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 output schema and no annotations, the description must explain the tool's purpose, inputs, and outputs. It does none of these. The tool has six parameters but no hint about which are needed, what the result list looks like, or how pagination works.

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 information about any of the six parameters. Schema coverage is only 33%, with only 'region' and 'project_id' having 'Overrides' descriptions. The description does not compensate for the lack of documentation on 'limit', 'offset', 'log_group_id', or 'log_stream_id'.

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 ListCharts' is essentially a restatement of the tool's name. It provides no verb beyond the name itself and no explanation of what 'Charts' refers to or what the operation does. It does not distinguish this 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?

There is no guidance on when to use this tool versus alternatives. No context is provided about prerequisites, typical scenarios, or how it relates to other LTS list operations like ListLogStreams or ListLogs.

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