ShowAdminConfig

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

No annotations are provided, and the description offers no behavioral details such as whether the operation is read-only, requires auth, or returns a specific result. The description carries no burden of transparency at all.

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 single sentence is short, but it is under-specified rather than concise since it does not earn its place by adding information beyond the tool name. It is not structured or front-loaded with useful content.

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 a tautological description, the tool is functionally opaque. Even though it has only two optional parameters, an agent cannot determine what ShowAdminConfig does or returns.

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 fully documents both parameters with 'Overrides HUAWEI_REGION' and 'Overrides HUAWEI_PROJECT_ID', so the schema covers 100% of parameter meaning. The description adds no parameter information, but the baseline for high schema coverage is 3.

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 merely restates the tool name ('Huawei Cloud LTS operation ShowAdminConfig') without specifying what the operation does. It provides no verb or resource beyond the name itself, making it a tautology.

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 given about when to use ShowAdminConfig vs any of the many sibling tools. The description is strictly a domain label and provides no context or exclusions.

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