remnawave_internal_squads_delete

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

Without annotations, the description does not disclose behavioral traits beyond labeling it a 'mutation'. It omits details like whether deletion is permanent, if confirmation is required, or what happens to related data. The term 'mutation' is generic and insufficient.

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 extremely brief but under-specifies critical information. It does not earn its place; it essentially repeats the tool name with added '(mutation)'. A longer description with essential details would improve usability.

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 has 4 parameters, including a nested 'payload' object and boolean flags, and no output schema, the description is completely inadequate. An agent cannot understand how to construct a valid request or what to expect in response.

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 input schema has 4 parameters with 0% description coverage, yet the description adds no meaning to any parameter. Parameters like payload, confirmToken, and mutationApproved remain unexplained, leaving the agent unable to determine how to invoke the tool correctly.

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 states it is a mutation for deleting internal squads, which aligns with the tool name and distinguishes it from external squads. However, it does not specify what identifier is used to select which squad to delete (e.g., by ID or name), leaving purpose slightly vague.

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 remnawave_internal_squads_list, remnawave_internal_squads_create, or the external squad deletion tool. The description fails to provide any context for appropriate usage.

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