DeleteLogStream

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 does not mention that the operation is destructive, whether it is reversible, what side effects occur (e.g., data loss), or what authentication is required. This is a complete absence of transparency.

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?

While the description is extremely short, it is under-specified to the point of being tautological. The single sentence adds no information beyond the tool name, so it does not earn its place as a useful description.

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 four parameters and no annotations or output schema, the description is drastically incomplete. It omits prerequisites, effects, error behavior, and parameter relationships, leaving the agent without the information needed to invoke the tool correctly.

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 provides descriptions for 'region' and 'project_id' but leaves 'log_group_id' and 'log_stream_id' undocumented. The description adds no additional meaning about these parameters, such as the hierarchical relationship between log groups and streams, or any constraints on their values.

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 DeleteLogStream' is a tautology that restates the tool name without specifying what the operation does (e.g., 'Deletes a log stream'). It does not distinguish this tool from sibling delete operations like DeleteLogGroup or DeleteTransfer.

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 context is provided about when to use this tool versus alternatives, no prerequisites are mentioned, and there is no guidance on required parameters or typical scenarios. The description is entirely silent on usage.

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