DeleteDashboard

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that deletion is likely destructive/irreversible, whether associated charts can be deleted, or any required permissions. The description adds no transparency about the operation's effects.

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 short, but this is under-specification rather than conciseness. The single sentence provides no useful information and does not earn its place, making it an empty tautology.

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 delete operation with 4 parameters, no annotations, and no output schema, the description is completely inadequate. It fails to explain return values, side effects, required context, or any meaningful details necessary for correct invocation.

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 only 50%, with 'id' and 'is_delete_charts' lacking descriptions. The description adds no additional meaning about parameter semantics, leaving the agent without a clear understanding of how to populate these fields.

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 DeleteDashboard' is a tautology that simply restates the tool name without explaining what the operation does, what a dashboard is, or what LTS is. It provides no specific verb+resource information beyond the tool's name.

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 like DeleteLogGroup or DeleteLogStream. The description does not indicate prerequisites, scenarios, or exclusions, leaving the agent with no contextual direction.

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