xgroup_destroy

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 only states 'destroy' without explaining side effects (e.g., whether pending messages are discarded), error handling (e.g., behavior on nonexistent group), or required permissions. This is insufficient for safe invocation.

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 (4 lines) and front-loaded with the core purpose. However, it could benefit from a structured format (e.g., bullet points) to improve readability for an AI agent.

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?

Given the tool's destructive nature and the presence of sibling tools like xgroup_create and xreadgroup, the description lacks critical context about prerequisites, error states, and the return value structure. The output schema exists but is not explained beyond 'returns str', leaving the AI agent underinformed.

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 restates parameter names and types from the schema ('key (str): The stream key.') without adding meaningful constraints, examples, or validation rules. Schema description coverage is 0%, so the description should compensate, but it fails to do so.

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 ('Destroy') and the resource ('a consumer group for a Redis stream'), making the tool's purpose immediately understandable. However, it does not elaborate on what 'destroy' entails or how it differs from other group operations like deleting the stream itself.

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 guidance is provided on when to use this tool, prerequisites (e.g., group must exist), or alternatives. For example, it does not mention that xgroup_destroy is the inverse of xgroup_create, nor does it advise against destroying an in-use group.

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