delete_data_stream

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

The description states that deletion is permanent and includes backing indices, which is important. However, it does not disclose other behavioral traits like authentication requirements, error handling, or performance impact. Since no annotations are provided, the description carries the full burden but only partially fulfills it.

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 concise: two sentences followed by a clean parameter list. The purpose is front-loaded, and every sentence adds value. No redundant information.

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 deletion tool, the description covers what is deleted, permanence, and parameter details. The output schema exists, so return values are documented elsewhere. The context is complete given the tool's complexity and the presence of sibling tools for related operations.

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 are described with additional context beyond the schema. The 'name' parameter clarifies it can be a comma-separated list or wildcard pattern, and 'cluster' explains the default behavior. Since schema description coverage is 0%, the description fully compensates.

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 tool name and description clearly indicate that it deletes data streams. The first sentence 'Delete one or more data streams' directly states the action and resource. It is distinct from sibling tools like 'delete_index' or 'delete_document'.

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?

The description explains that deletion is permanent and supports comma-separated lists or wildcard patterns, but does not provide explicit guidance on when to use this tool versus alternatives or mention prerequisites or exclusions.

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