List KooCLI operations for a Huawei Cloud service by running local/read-only hcloud --help.
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes | KooCLI service name, such as ECS, VPC, IMS, OBS, RDS, or CDN. | |
| timeoutMs | No | Optional timeout in milliseconds. Defaults to 60000. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosing side effects. It explicitly notes the operation is 'local/read-only', which signals safety and non-mutation, though it does not elaborate on failure modes or prerequisites.
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, focused sentence with no redundant wording. It fronts the primary action and includes the key qualifier 'local/read-only' early.
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?
For a simple listing tool with one required parameter and no output schema, the description is sufficient: it covers what, target, and safety. It could be improved by adding explicit guidance on when to use it versus related command-execution tools.
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?
Both parameters already have clear descriptions in the schema (service name and timeout), and the tool description does not add extra meaning beyond that. Schema coverage is effectively 100%, so baseline 3 applies.
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 clearly states the action ('List'), the object ('KooCLI operations'), and the target ('a Huawei Cloud service'), which distinguishes it from sibling tools like listing regions or running commands.
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?
It explains the mechanism ('by running local/read-only hcloud <Service> --help') but does not explicitly say when to prefer this tool over alternatives such as planning or running commands. The intended use is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.