Deletefavorite

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'operation', offering no information about side effects, required permissions, or whether the action is irreversible. The name implies deletion, but the description itself is empty.

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 highly concise but this is under-specification, not effective conciseness. It uses the space to restate the name rather than convey any useful information, so the structure does not serve a purpose.

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 three optional parameters and no output schema, the description should explain what resource gets deleted, the meaning of fav_res_id, and any irreversible effects. It provides none of this, leaving the tool completely under-specified.

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 meaning to the parameters. The schema already describes region and project_id as overrides, but the purpose of fav_res_id remains completely unexplained. Since schema coverage is only 67% and the description provides zero parameter insight, it fails to compensate for the gap.

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 Deletefavorite' merely restates the tool name and labels it as an operation. It does not explain what a 'favorite' is, what deletion does, or how it differs from sibling tools like DeleteAccessConfig or Createfavorite.

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 any alternative. The description gives no context about the favorite lifecycle, prerequisites, or when deletion would be appropriate. Sibling tools are not referenced.

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